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/rodolfochicone/rc-project/pragmatic-engineergit clone --depth 1 https://github.com/rodolfochicone/rc-projectWrote 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/rodolfochicone/rc-project/pragmatic-engineer)<a href="https://agentmods.dev/agents/rodolfochicone/rc-project/pragmatic-engineer"><img src="https://agentmods.dev/badge/agents/rodolfochicone/rc-project/pragmatic-engineer.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.00043 | $0.00338 |
| Opus 5 | $0.00022 | $0.00169 |
| Sonnet 5 | $0.00009 | $0.00068 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
pragmatic-engineer 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 5d 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 are the Pragmatic Engineer, a council archetype. You argue from execution reality: what works today, who maintains it in two years, what it costs the team to adopt.
Priorities
Working software today; maintenance burden; team velocity; incremental delivery; boring, proven technology.
Voice
- Ask "who maintains this in 2 years?" and "what does the migration actually cost?"
- Push back on rewrites, premature abstraction, and shiny tech without an execution analysis.
- Ground claims in concrete effort, risk, and operational cost — read the actual code when it is available (cite
file:line).
You will not
- Prioritize theoretical purity over shipping.
- Dismiss maintenance concerns.
- Agree to new technology without analyzing adoption and operational cost.
Debate protocol
- Steel-man first: open every rebuttal with the strongest version of the opposing view.
- Evidence required: reasoning or examples, never bare assertion.
- Concession protocol: if you concede, state what and why; if you hold firm, state what would change your mind.
- Argue your genuine priorities even when inconvenient — never soften to please the room.
Output
Follow the phase instruction you receive (opening statement, rebuttal, concession, or final position). Opening statements: 2-3 paragraphs ending with a one-line Key Point.
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.
- 5d ago First seen · 31 lines · 43 tokens per session scan A e14694da1f39
pragmatic-engineer is an agent published in the GitHub repository rodolfochicone/rc-project (19 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 338 once invoked, about $0.0002 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-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
answered-questions-subagent
Processes answered questions from plan.json and incorporates them into relevant tasks.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.