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/tae0y/python-project-template/tdd-guardiangit clone --depth 1 https://github.com/tae0y/python-project-templateWhat 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.00051 | $0.02712 |
| Opus 5 | $0.00026 | $0.01356 |
| Sonnet 5 | $0.00010 | $0.00542 |
| Haiku 4.5 | $0.00005 | $0.00271 |
Grade A, and why
tdd-guardian 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 359 lines · 51 tokens per session scan A 6593f9347b75
tdd-guardian is an agent published in the GitHub repository tae0y/python-project-template (14 stars, last pushed 25d ago), with no licence file. It adds 51 tokens to every session and 2,712 once invoked, about $0.0003 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 agents, from other repositories
qa
Use this agent when you need a strict, independent quality gate review of recently written code against the PRD and API documentation. This agent acts as a ruthless test engineer who reads only the PRD and API docs, then verifies whether the implementation meets every requirement — functional completeness, edge cases…
prd-plan
Use this agent when the user describes a feature idea, product requirement, or technical initiative and needs a comprehensive plan developed from it. This agent transforms rough concepts and PRDs into detailed, actionable implementation plans that account for edge cases, dependencies, and risks.\n\n \nContext: The…
dev
Use this agent when the user provides PRD documents, API documentation, prd-plan specifications, or QA requirements and expects them to be implemented fully without questions or explanations. This agent executes requirements end-to-end: reads the specification, implements the code, writes tests, and verifies…
tdd-coach
Guides test-driven development with red-green-refactor discipline. Use when implementing features or fixes with TDD.
tester
Evaluate NL artifacts against test specifications. Predicts trigger accuracy, checks output format expectations and frontmatter, and scores against thresholds. Context: Developer wrote a spec for a new agent and wants to check if it passes user: "/nlpm:test" assistant: "I'll use the tester to evaluate your artifacts…
pr-crisis-response-agent
Takes a crisis situation briefing and produces a complete crisis communications package — from an immediate holding statement through full crisis statement, FAQ document, spokesperson briefing, internal staff memo, and (where appropriate) proactive media outreach and a formal press release — ready for the comms team…