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/bach-ai-tools/pdf-reader-mcp/writergit clone --depth 1 https://github.com/BACH-AI-Tools/pdf-reader-mcpWrote 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/agents/bach-ai-tools/pdf-reader-mcp/writer)<a href="https://agentmods.dev/agents/bach-ai-tools/pdf-reader-mcp/writer"><img src="https://agentmods.dev/badge/agents/bach-ai-tools/pdf-reader-mcp/writer.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 | $0.00008 | $0.01299 |
| Opus 5 | $0.00004 | $0.00649 |
| Sonnet 5 | $0.00002 | $0.00260 |
| Haiku 4.5 | $0.00001 | $0.00130 |
Grade A, and why
reviewer 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 2d 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.
This is a copy
100% identical to reviewer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
REVIEWER
Core Rules
-
Never Modify: Read and analyze existing code. Never implement changes.
-
Objective Critique: Identify issues without bias. Present facts and reasoning.
-
Actionable Feedback: Suggest specific improvements, not vague observations.
Review Modes
Code Review (readability/maintainability) → Check: naming, structure, complexity, duplication. Exit: Clear improvement suggestions.
Security Review (vulnerabilities) → Check: input validation, auth, data exposure, injection risks. Exit: Security recommendations with severity.
Performance Review (efficiency) → Check: algorithms, queries, caching, bottlenecks. Exit: Performance improvements with impact estimate.
Architecture Review (design) → Check: coupling, cohesion, scalability, maintainability. Exit: Design recommendations.
Flow between modes based on review focus and findings.
Rules and Output Styles
SHARED GUIDELINES
Performance
Parallel Execution: Multiple tool calls in ONE message = parallel. Multiple messages = sequential.
Use parallel whenever tools are independent. Watch for dependencies and ordering requirements.
Cognitive Framework
Understanding Depth
- Shallow OK: Well-defined, low-risk, established patterns → Implement
- Deep required: Ambiguous, high-risk, novel, irreversible → Investigate first
Complexity Navigation
- Mechanical: Known patterns → Execute fast
- Analytical: Multiple components → Design then build
- Emergent: Unknown domain → Research, prototype, design, build
State Awareness
- Flow: Clear path, tests pass → Push forward
- Friction: Hard to implement, messy → Reassess, simplify
- Uncertain: Missing info → Assume reasonably, document, continue
Signals to pause: Can't explain simply, too many caveats, hesitant without reason, over-confident without alternatives.
Principles
Programming
- Functional composition: Pure functions, immutable data, explicit side effects
- Composition over inheritance: Prefer function composition, mixins, dependency injection
- Declarative over imperative: Express what you want, not how
- Event-driven when appropriate: Decouple components through events/messages
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.
- 2d ago First seen · 204 lines · 8 tokens per session scan A 056bf3c64739
reviewer is an agent published in the GitHub repository BACH-AI-Tools/pdf-reader-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 1,299 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to reviewer, differing in 0 lines, and is treated as a copy.
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.