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/talayash/agentrium/tddgit clone --depth 1 https://github.com/talayash/agentriumWhat 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.00000 | $0.00359 |
| Opus 5 | $0.00000 | $0.00179 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
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 2d 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
TDD
Implement a feature using strict Test-Driven Development.
Instructions
Implement the following using TDD: $ARGUMENTS
The TDD Cycle
Follow this cycle strictly. Do NOT skip steps.
🔴 RED - Write a Failing Test
- Write a test that describes the desired behavior
- Run the test - it MUST fail
- If it passes, the test is wrong or the feature already exists
🟢 GREEN - Make It Pass
- Write the MINIMUM code to make the test pass
- Do not write more code than needed
- Run the test - it MUST pass now
🔵 REFACTOR - Clean Up
- Refactor the implementation (not the test) for clarity
- Run the test - it MUST still pass
- No behavior changes during refactor
Repeat
Continue the RED → GREEN → REFACTOR cycle for each piece of functionality.
For This Project
Frontend tests (if applicable):
- Use Vitest for unit tests
- Test React components with @testing-library/react
- Test Zustand stores directly
Backend tests (if applicable):
- Use
#[cfg(test)]modules in Rust - Test command logic without Tauri runtime where possible
- Use mock implementations for Database/TerminalManager
Checkpoints
Create a git checkpoint after each completed GREEN phase:
git add -A && git commit -m "checkpoint: [test description] - GREEN"
Report
After implementation:
## TDD Report
- Tests written: N
- All passing: ✅/❌
- Cycles completed: N
- Coverage: [estimate]
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.
- 2d ago First seen · 58 lines · 0 tokens per session scan A 49c0205ded18
tdd is a command published in the GitHub repository talayash/agentrium (39 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 359 tokens. 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
spec-impl
Execute spec tasks using TDD methodology.
run
Implement SPEC requirements using DDD/TDD methodology.
spec-design
Create comprehensive technical design for a specification.
tdd-refactor
TDDのRefactorフェーズを実行します。テストを通す実装が完了した後、コード品質の改善とリファクタリングを行います。.
validate-gap
Analyze implementation gap between requirements and existing codebase.
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).