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 skills/rafmacalaba/armada/armada-tddnpx skills add rafmacalaba/armada --skill armada-tddgit clone --depth 1 https://github.com/rafmacalaba/armadaWrote 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/skills/rafmacalaba/armada/armada-tdd)<a href="https://agentmods.dev/skills/rafmacalaba/armada/armada-tdd"><img src="https://agentmods.dev/badge/skills/rafmacalaba/armada/armada-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 | $0.00036 | $0.00272 |
| Opus 5 | $0.00018 | $0.00136 |
| Sonnet 5 | $0.00007 | $0.00054 |
| Haiku 4.5 | $0.00004 | $0.00027 |
Grade A, and why
armada-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 5d 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
Armada: Test-Driven Development
Write the test first. Watch it fail. Write the minimal implementation to pass. Refactor. Never skip the failing-test step. This is the only acceptable workflow for implementation code.
Rules
- Write a failing test before any implementation. The test must exercise the desired behavior, not the implementation details.
- Run the test and confirm it fails for the right reason (feature missing, not a syntax error). Never skip this step.
- Write the minimal code to make the test pass. Do not add features, error handling, or performance optimizations that the test does not demand.
- Refactor only after all tests are green. Remove duplication, improve names, but add no behavior.
- One test per behavior. Tests live in
tests/*.test.jsnext to the source. If a bug is found, write a failing test that reproduces it before fixing.
Example: To add validateSkillName(name): write test("rejects names with uppercase"), run it (fail), write the ^[a-z] regex, run it (pass).
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.
- 5d ago First seen · 19 lines · 0 tokens per session scan A 3616d1fdcc30
armada-tdd is a skill published in the GitHub repository rafmacalaba/armada (93 stars, last pushed 7d ago), licensed MIT. It adds 36 tokens to every session and 272 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 skills, from other repositories
tdd-rust
TDD workflow for RTK filter development. Red-Green-Refactor with Rust idioms. Real fixtures, token savings assertions, snapshot tests with insta. Auto-triggers on new filter implementation.
rtk-tdd
Enforces TDD (Red-Green-Refactor) for Rust development. Auto-triggers on implementation, testing, refactoring, and bug fixing tasks. Provides Rust-idiomatic testing patterns with anyhow/thiserror, cfg(test), and Arrange-Act-Assert workflow.
aoe
Use when launching, monitoring, or controlling AI coding agents (Claude Code, Codex, OpenCode, etc.) in tmux via Agent of Empires (aoe). Covers creating sessions, capturing agent output, running parallel worktree agents, and organizing work into groups and profiles. Prefer aoe over raw tmux for agent management.
test-driven-development
在实现任何功能或修复 bug 时使用，在编写实现代码之前.
test-driven-development
Use when the user explicitly requests strict or test-first TDD, or when the current conversation already contains an explicit TDD Route: strict decision from another Aegis workflow.
old-coder
Evidence-first development — surround the implementation with an executable spec and a gauntlet of constraints (tests, types, coverage, mutation) so line-by-line review becomes optional. Use when the user explicitly asks for high-assurance or evidence-first work ("reliable", "TDD", "prove it works", "I won't read the…