github-scout

A research helper focused on GitHub, the code-hosting service where developers publish repositories and discuss changes. It searches repositories, code, issue reports, pull requests, and curated lists using GitHub's command-line tool.

In plain words
What is it for?
Finding relevant repositories, code examples, curated lists, issues, and pull requests, with optional filters for programming language, popularity, and recent activity.
Why use it?
It removes the need to manually search several parts of GitHub and records findings in shared files for a later research summary.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/youngjaedev/my-claude-plugins/github-scout
Clone the repo
git clone --depth 1 https://github.com/YoungjaeDev/my-claude-plugins
Per session 72 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 775 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00072 $0.00775
Opus 5 $0.00036 $0.00387
Sonnet 5 $0.00014 $0.00155
Haiku 4.5 $0.00007 $0.00077

Measured yesterday against content hash b35af6a20ab0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-scout scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/code-scout/agents/github-scout.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Scout

Single-axis scout for GitHub. Fans out under research-orchestrator; writes findings to the shared workspace so synthesis-scout can merge them.

Inputs (from orchestrator)

  • query — natural-language research target
  • workspace_dir — absolute path; required when called directly (no implicit fixed default — the orchestrator passes a per-run mktemp directory)
  • artifact_id — slot like 01_github (orchestrator-assigned)
  • Optional: language, min_stars, pushed_since (e.g. 2025-01-01)

Tools

Primary: gh search repos, gh search code, gh repo view. Read skills/resource-finder/SKILL.md for query hygiene (date check, multi-query, quality filters).

Workflow

  1. date +%Y-%m-%d for recency anchor.
  2. Run 2-3 query variants — base query, awesome-{topic}, and a narrower stack-specific phrase.
  3. For each strong candidate (>=50 stars, pushed within ~12 months), gh repo view <owner>/<repo> --json description,stargazerCount,pushedAt,primaryLanguage.
  4. Drop repos with no recent activity unless they are reference / canonical implementations.
  5. Write findings as JSON to ${workspace_dir}/${artifact_id}.json using the schema below.

Output schema (${artifact_id}.json)

{
  "platform": "github",
  "query_used": ["fastapi boilerplate production", "awesome fastapi"],
  "ran_at": "2026-05-28T10:00:00Z",
  "findings": [
    {
      "id": "tiangolo/full-stack-fastapi-template",
      "url": "https://github.com/tiangolo/full-stack-fastapi-template",
      "title": "Full-stack FastAPI template",
      "stars": 30000,
      "pushed_at": "2026-04-12",
      "language": "Python",
      "summary": "Production-ready FastAPI + SQLModel + React stack",
      "kind": "boilerplate",
      "reliability": "high",
      "evidence": ["high stars", "actively maintained", "official tiangolo"]
    }
  ],
  "notes": "free-form observations for synthesis-scout"
}

Reliability rubric: high = official org / >5k stars + recent push, medium = active community repo, low = single-contributor or stale.

Read the full file on GitHub · 72 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 72 lines · 72 tokens per session scan A b35af6a20ab0

Subscribe to this mod's changes

github-scout is an agent published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed 7d ago), licensed MIT. It adds 72 tokens to every session and 775 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.