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/bach-ai-tools/pdf-reader-mcp/explaingit clone --depth 1 https://github.com/BACH-AI-Tools/pdf-reader-mcpWhat 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.00004 | $0.00157 |
| Opus 5 | $0.00002 | $0.00078 |
| Sonnet 5 | $0.00001 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
explain 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.
What it actually says
Explain Code
Context
$ARGUMENTS
Your Task
Provide a comprehensive explanation of the code above (or at the specified location) that includes:
-
Overview
- What does this code do?
- What problem does it solve?
-
How It Works
- Step-by-step breakdown of the logic
- Key algorithms or patterns used
- Important design decisions
-
Components
- Main functions/classes/modules
- Their roles and responsibilities
- How they interact
-
Important Details
- Edge cases handled
- Performance considerations
- Security implications
- Dependencies and requirements
Use clear language and provide examples where helpful.
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 · 39 lines · 4 tokens per session scan A d8ac3d0c5b63
explain is a command published in the GitHub repository BACH-AI-Tools/pdf-reader-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 4 tokens to every session and 157 once invoked, about $0.0000 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-09-01.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.