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 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/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/skills/rafmacalaba/armada/armada-tdd"><img src="https://agentmods.dev/badge/skills/rafmacalaba/armada/armada-tdd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.00272 |
| Opus 5.5 | $0.00014 | $0.00109 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 19 lines · 0 tokens per session scan A 3616d1fdcc30
armada-tdd is a skill published in the GitHub repository rafmacalaba/armada (104 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 272 once invoked, about $0.0001 per session on Opus 5.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
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
implement
Use when an approved plan and task list exist and it is time to turn them into working, tested code — the SDD phase after analyze and before verify. Enforces TDD: a failing test comes before the code that makes it pass, one task at a time, appended to a progress ledger that survives compaction. Delegates test tooling…
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…
implement
TDD implementation - make failing tests pass.
test-driven-development
Use when user explicitly requests test-driven development. Triggers: 'TDD', 'write tests first', 'red green refactor', 'test-first', 'start with the test'. Also invoked by develop and executing-plans for implementation tasks. NOT for: full feature work (use develop, which includes TDD internally).
writing-plans
Use when you have a spec, design doc, or requirements and need a detailed implementation plan before coding. Triggers: 'write a plan', 'create implementation plan', 'plan this out', 'break this down into steps', 'convert design to tasks', 'implementation order'. Also invoked by develop during planning. NOT for…