Repo Scanner

What Repo Scanner is

Repo Scanner is a subagent published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Repo Scanner and get back a compact result.

It is set up to use these tools: Read, Glob, Grep, triage:search_issues, triage:inspect_recent_commits, triage:inspect_code_paths, triage:check_recent_deploys. Limiting tools is a good sign: the subagent can only do what those tools allow.

How to install Repo Scanner

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/mcp/x-bug-triage/agents/repo-scanner.md, shared under the repository's MIT license. Read the full file on GitHub.

{
  "cluster_id": "c1",
  "repos_scanned": ["org/repo-a", "org/repo-b"],
  "evidence": [
    { "repo": "org/repo-a", "evidenceType": "issue_match", "tier": 2, "title": "...", "confidence": 0.75, "description": "..." },
    { "repo": "org/repo-a", "evidenceType": "recent_deploy", "tier": 3, "title": "...", "confidence": 0.5, "description": "..." }
  ],
  "external_dependency_flag": false,
  "warnings": []
}

Before you install

• Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
• Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
• Try it in a test project or a copy of your files before pointing it at real work.
• Pin the version you tested, and review changes before updating.
• Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ