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 commands/guanyang/open-agent-hub/test-tddgit clone --depth 1 https://github.com/guanyang/open-agent-hubWrote 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/guanyang/open-agent-hub/test-tdd)<a href="https://agentmods.dev/commands/guanyang/open-agent-hub/test-tdd"><img src="https://agentmods.dev/badge/commands/guanyang/open-agent-hub/test-tdd.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.00032 | $0.00267 |
| Opus 5 | $0.00016 | $0.00133 |
| Sonnet 5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
test-tdd 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 6d 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
Slash Command: /test-tdd
Core Objective
Locate and execute the test suites corresponding to modified files.
Steps for the Agent
- Identify Modified Code: Run
git statusorgit diff --name-onlyto identify source code files that have changed. - Find Matching Tests: Search for matching test files in the project. For example:
foo.js➔ search forfoo.test.js,foo.spec.js,test_foo.jsintest/,spec/, or local directories.
- Deduce Test Command: Determine the correct command runner based on
package.jsonscripts or file types (e.g.,npm test -- <file>,npx jest <file>,pytest <file>,go test <file>). - Execute: Run the test command and display the execution results.
- Loop Strategy:
- If tests fail, suggest invoking agent-debugger to inspect stack traces.
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.
- 6d ago First seen · 19 lines · 32 tokens per session scan A ce04fa928a50
test-tdd is a command published in the GitHub repository guanyang/open-agent-hub (959 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 267 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 commands, from other repositories
pm-tests
List missing unit-test companions for core/changed sources. Do not write tests into the business tree unless the user confirms.
create-widget
Create a Flutter widget with proper state management and Material/Cupertino design.
create-component
Create a frontend component with proper structure, types, and accessibility.
implementar
Ejecutar tareas TDD fase por fase dentro de Docker hasta que todos los tests pasen.
simplify-fn
Refactor a complex function to reduce cyclomatic complexity.
verify
Run the full verification suite (build, type-check, tests, lint) via a fresh-context verification-runner subagent; reports evidence paths. Read-only by default; opt-in '--fix' runs a bounded auto-fix loop (max 2 cycles). Use before marking featurelist.json status as 'pass'.