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 skills add sawrus/agent-guides --skill repo-scangit clone --depth 1 https://github.com/sawrus/agent-guidesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sawrus/agent-guides/repo-scan)<a href="https://agentmods.dev/skills/sawrus/agent-guides/repo-scan"><img src="https://agentmods.dev/badge/skills/sawrus/agent-guides/repo-scan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sawrus/agent-guides/repo-scan"><img src="https://agentmods.dev/badge/skills/sawrus/agent-guides/repo-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00106 | $0.01080 |
| Opus 5.5 | $0.00042 | $0.00432 |
| Sonnet 5.5 | $0.00021 | $0.00216 |
| Haiku 4.5 | $0.00011 | $0.00108 |
Grade A, and why
repo-scan 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 3d ago.
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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repo-scan
Runs tools/repo-scan of agent-guides through the wrapper <skill base>/scripts/repo-scan.sh (path relative to
this skill's directory). The wrapper finds agent-guides (or clones it), checks requirements, applies the settings
and calls the tool.
- Stage 1 (
scan) is static and offline. It never runs code of the analyzed repositories and never commits to them. - Stage 2 (
llm) sends the stage 1 summary and short excerpts (README, Makefile, CI) to an LLM. rundoes both stages in one command.
Parameters (ask the user when unclear)
| User asks for | Command |
|---|---|
| one repository, both stages | repo-scan.sh run <repo dir> |
| one repository, static only | repo-scan.sh scan <repo dir> |
| many repositories, both stages | repo-scan.sh run [<group dir> ...] (no arguments: REPO_SCAN_ROOTS) |
| many repositories, static only | repo-scan.sh scan [<group dir> ...] |
| LLM over an earlier scan | repo-scan.sh llm [<repo> ...] [--limit N] |
| gate candidates / verification | repo-scan.sh gate-propose [<repo> ...] / repo-scan.sh gate-verify <repo> ... |
- A repository directory is the focus: the context roots (
REPO_SCAN_CONTEXT_ROOTS, defaultREPO_SCAN_ROOTS) are scanned so its links resolve, and only its view is written. - Provider:
--provider claude --model haiku|sonnet|opus(defaultclaude, modelhaiku) or--provider litellm(needsAGENTIC_LLM_BASE_URL,AGENTIC_LLM_API_KEYand a model). - Output:
--out DIR(default~/.cache/agentic/repo-scan/<repo name>or.../all). - Settings live in
~/.config/agentic/repo-scan.env(REPO_SCAN_ROOTS,REPO_SCAN_ROOT_URLS,REPO_SCAN_CONTEXT_ROOTS,REPO_SCAN_PROVIDER,REPO_SCAN_MODEL,AGENTIC_LLM_BASE_URL,AGENTIC_LLM_MODEL).
Workflow
Step 1 - requirements
bash <skill base>/scripts/repo-scan.sh check
Exit 1 means python3 >= 3.11 or git is missing: show the printed install command and stop. If scc is
missing, offer bash <skill base>/scripts/repo-scan.sh tools (exact line counts); without it a built-in counter runs.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 83 lines · 106 tokens per session scan A f3d89cafbeb5
repo-scan is a skill published in the GitHub repository sawrus/agent-guides (19 stars, last pushed yesterday), licensed MIT. It adds 106 tokens to every session and 1,080 once invoked, about $0.0004 per session on Opus 5.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-10-27.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
antigravity-maintainer-batch-release
Run protected AAS maintainer sweeps, PR merge batches, resumable review, immutable distribution, Core checks, and scripted releases. Use for repository maintenance, main alignment, CLI/MCP/Workbench changes, or release work; not ordinary contribution tasks.
ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
app-store-changelog
Generate user-facing App Store release notes from git history since the last tag.
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
git-workflow
Trunk-based development with atomic commits, clean history, and meaningful commit messages. Every commit should be deployable.