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 commands/amey-thakur/ai-skills/agent-explain-codebasegit clone --depth 1 https://github.com/Amey-Thakur/AI-SKILLSWrote 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/amey-thakur/ai-skills/agent-explain-codebase)<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/agent-explain-codebase"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/agent-explain-codebase.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.00025 | $0.00424 |
| Opus 5 | $0.00013 | $0.00212 |
| Sonnet 5 | $0.00005 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
agent-explain-codebase 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 6d 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
You were invoked as a slash command. The user's input:
$ARGUMENTS
Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.
You are a coding agent. Map this codebase so I can work in it confidently. Ground every claim in the actual code, not assumptions.
CODEBASE: {codebase}
WHAT I NEED TO UNDERSTAND: {focus}
Investigate and report:
- The big picture: what this codebase does, its architecture, and the main components and how they fit together. Point to the entry points and the directories that matter.
- The path that answers my focus: if I asked how feature X works or where to change Y, trace the actual flow through the real files and functions (name them, with paths), from entry to exit.
- The conventions: the patterns, styles, and idioms this codebase uses that I should follow (how it handles errors, state, tests, config), so any change fits in.
- The landmarks and hazards: the key files to know, the tricky or fragile parts, and where NOT to break things.
- If I named a change I want to make: where it should go and what it would touch.
Rules: ground everything in the real code (cite files and functions, do not generalize from the framework's defaults). Distinguish what you verified from what you inferred. If something is unclear or you could not find it, say so rather than guessing. Be concrete and specific: the goal is that I can act on this, not admire a summary. Keep it focused on what I asked, not a tour of everything.
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.
- 6d ago First seen · 44 lines · 25 tokens per session scan A 9518bc8f5bb1
agent-explain-codebase is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (7 stars, last pushed 7d ago), licensed MIT. It adds 25 tokens to every session and 424 once invoked, about $0.0001 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 commands, from other repositories
ui5-version
Display UI5 version information, support status, release notes, and upgrade paths.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.