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.
npx agentmods add agents/youngjaedev/my-claude-plugins/github-scoutgit clone --depth 1 https://github.com/YoungjaeDev/my-claude-pluginsWhat 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.
| Model | Per session | Once 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 |
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.
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 targetworkspace_dir— absolute path; required when called directly (no implicit fixed default — the orchestrator passes a per-runmktempdirectory)artifact_id— slot like01_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
date +%Y-%m-%dfor recency anchor.- Run 2-3 query variants — base query,
awesome-{topic}, and a narrower stack-specific phrase. - For each strong candidate (>=50 stars, pushed within ~12 months),
gh repo view <owner>/<repo> --json description,stargazerCount,pushedAt,primaryLanguage. - Drop repos with no recent activity unless they are reference / canonical implementations.
- Write findings as JSON to
${workspace_dir}/${artifact_id}.jsonusing 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.
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.
- yesterday First seen · 72 lines · 72 tokens per session scan A b35af6a20ab0
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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.