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.
git clone --depth 1 https://github.com/hamzafarooq/claude-code-starterWrote 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/commands/hamzafarooq/claude-code-starter/explain-me-a-repo)<a href="https://agentmods.dev/commands/hamzafarooq/claude-code-starter/explain-me-a-repo"><img src="https://agentmods.dev/badge/commands/hamzafarooq/claude-code-starter/explain-me-a-repo.svg" alt="Measured on agentmods" 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.00000 | $0.00407 |
| Opus 5 | $0.00000 | $0.00204 |
| Sonnet 5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
explain-me-a-repo 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 8d 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.
What it actually says
If a GitHub repo URL was not provided, ask the user for one now.
Then:
- Use Brave MCP to navigate to the repo URL —
mcp__brave-devtools__browser_navigate - Take a snapshot to read the page —
mcp__brave-devtools__browser_snapshot - Navigate to the raw README if visible — look for README.md link and navigate to it
- Explore key folders by navigating to subdirectories as needed (src/, app/, main files, config)
- Close the browser when done —
mcp__brave-devtools__browser_close
Produce the following write-up directly — no preamble:
[Repo Name]
URL: [GitHub URL] Language(s): [Primary languages used]
What it does
One paragraph. Plain English. What problem does this repo solve? Who would use it?
How it works (high level)
2-4 bullet points explaining the architecture or flow. No code. Focus on concepts.
Key files and folders
A short table:
| Path | What it does |
|---|---|
| ... | ... |
Who it's for
One sentence. Developer? PM? Data scientist? End user?
How to get started
Copy the "Quick Start" or "Installation" steps from the README verbatim, or summarize if there is none. Maximum 5 steps.
Interesting things to note
2-3 observations: unusual design choices, dependencies worth knowing about, anything a PM should flag.
Rules:
- Use plain English throughout — no code unless quoting directly from the repo
- If the README is missing or thin, say so and work from what you can find in the file structure
- If you cannot access the repo (private, 404, etc.), tell the user clearly and stop
- After the write-up, ask: "Want me to save this to docs/repo-summary.md?"
$ARGUMENTS
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.
- 8d ago First seen · 48 lines · 0 tokens per session scan A 868cc03731aa
explain-me-a-repo is a command published in the GitHub repository hamzafarooq/claude-code-starter (141 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 407 tokens. 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.