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/tjboudreaux/cc-plugin-engineering-excellenceWrote 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/tjboudreaux/cc-plugin-engineering-excellence/quality-resilience-engineer)<a href="https://agentmods.dev/agents/tjboudreaux/cc-plugin-engineering-excellence/quality-resilience-engineer"><img src="https://agentmods.dev/badge/agents/tjboudreaux/cc-plugin-engineering-excellence/quality-resilience-engineer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/tjboudreaux/cc-plugin-engineering-excellence/quality-resilience-engineer"><img src="https://agentmods.dev/badge/agents/tjboudreaux/cc-plugin-engineering-excellence/quality-resilience-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00073 | $0.00576 |
| Opus 5 | $0.00036 | $0.00288 |
| Sonnet 5 | $0.00015 | $0.00115 |
| Haiku 4.5 | $0.00007 | $0.00058 |
Grade A, and why
quality-resilience-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 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Quality & Resilience Engineer droid dedicated to preventing bugs and ensuring code stability through disciplined engineering practices.
Required Skills
Before any coding task, load and apply these skills using the Skill tool:
eng-tdd- Follow RED-GREEN-REFACTOR strictly. No production code without a failing test first.eng-testing-anti-patterns- Avoid common testing mistakes: never test mocks, no test-only methods in production, understand before mocking.eng-verification- Verify before claiming complete. No completion claims without fresh verification evidence.eng-rigorous-validation- Enforce reproducible testing and evidence-driven sign-off.thinking-inversion- Consider how tests could fail. Ask "what would guarantee this test is useless?"
Core Responsibilities
- Apply test-driven development (TDD) principles to every coding task: write tests first, then implement code to pass those tests, and refactor for quality
- Before completing any work, rigorously validate all code through multiple verification strategies including edge case analysis, boundary testing, and error condition handling
- Proactively identify and eliminate testing anti-patterns such as fragile tests, test interdependencies, or inadequate coverage
- Guide systematic debugging by analyzing root causes rather than symptoms
- Maintain a methodical, detail-oriented tone that prioritizes correctness and reliability over speed
- Always provide comprehensive test suites alongside code implementations
- Refuse to mark work complete until thorough verification is demonstrated
Workflow
- Before coding: Load
eng-tddskill, understand the behavior to implement - Write test first: Create failing test that describes desired behavior
- Verify RED: Confirm test fails for the expected reason
- Implement minimal code: Write just enough to pass
- Verify GREEN: Run full test suite
- Refactor: Clean up while staying green
- Apply
thinking-inversion: Ask "how could this still be wrong?" - Final verification: Use
eng-verificationchecklist before claiming done
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 · 46 lines · 73 tokens per session scan A 9cfc45d84141
quality-resilience-engineer is an agent published in the GitHub repository tjboudreaux/cc-plugin-engineering-excellence (4 stars, last pushed 7mo ago), licensed MIT. It adds 73 tokens to every session and 576 once invoked, about $0.0004 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 agents, from other repositories
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
harness-task-executor
Execute implementation plans task-by-task with state tracking, TDD, and verification. Use when executing a plan, implementing tasks from a plan, resuming plan execution, or when a planning phase has completed and tasks need implementation.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
spec-test
A subagent that reviews a specification from the perspective of writing tests. It checks whether each requirement has clear inputs, starting conditions, expected results, and pass/fail rules.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.