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/iamironz/ai-config-bundleWrote 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/commands/iamironz/ai-config-bundle/implement_tests)<a href="https://agentmods.dev/commands/iamironz/ai-config-bundle/implement_tests"><img src="https://agentmods.dev/badge/commands/iamironz/ai-config-bundle/implement_tests/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/commands/iamironz/ai-config-bundle/implement_tests"><img src="https://agentmods.dev/badge/commands/iamironz/ai-config-bundle/implement_tests.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.00000 | $0.00068 |
| Opus 5.5 | $0.00000 | $0.00027 |
| Sonnet 5.5 | $0.00000 | $0.00014 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
implement_tests 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 1mo 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
86% identical to commit — 4 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.
What it actually says
Implement Tests
Input
Use the text the user typed after the command name as the request for this command.
- Treat it as the command input for the shared command doc.
Instructions
Read and follow ai-kb/commands/implement_tests.md (canonical). If there is a conflict, prefer the shared doc.
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.
- 1mo ago First seen · 12 lines · 0 tokens per session scan A 108949220d76
implement_tests is a command published in the GitHub repository iamironz/ai-config-bundle (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 68 tokens. A static security scan graded it A with 0 findings. It is 86% identical to commit, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
fix-tests
Focus on all unit + command tests (pytest --exclude tests/integration). Make sure they pass and fix errors. If you run into anything very odd: stop, and let me know. Mutate test code first and let me know if you think you should update application code.
testgen-flow-data-collection
Phase 1 Data Collection of testgen-flow.
testgen-flow-gap-and-contradiction-analysis
Phase 2 Gap & Contradiction Analysis of testgen-flow.
testgen-flow-requirements-document-generation
Phase 4 Requirements Document of testgen-flow.
api-aqa-flow
Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.
api-aqa-flow-api-spec-analysis
Phase 2 API Spec Analysis of api-aqa-flow.