Borrowing it
Nothing to install: this file belongs to arrrrny/zuraffa. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/arrrrny/zuraffa/master/.agents/skills/speckit-tdd-setup/SKILL.mdgit clone --depth 1 https://github.com/arrrrny/zuraffaWrote 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/arrrrny/zuraffa/speckit-tdd-setup)<a href="https://agentmods.dev/skills/arrrrny/zuraffa/speckit-tdd-setup"><img src="https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-tdd-setup/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/arrrrny/zuraffa/speckit-tdd-setup"><img src="https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-tdd-setup.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.00037 | $0.00710 |
| Opus 5 | $0.00018 | $0.00355 |
| Sonnet 5 | $0.00007 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
speckit-tdd-setup 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Setup (zfa-aware)
Make this repository's test stack explicit, so every later TDD command runs real commands instead of guessing. In zuraffa-wired projects, the profile records zfa as the engine — raw dart/flutter commands appear only as what zfa itself invokes.
User Input
$ARGUMENTS
--no-constitution: skip Phase 4.--constitution-only: profile already correct, only handle the constitution.
Step 0 — Detect zuraffa
zfa --version 2>/dev/null && test -f .zfa.json && echo "ZFA_OK" || echo "ZFA_MISSING"
Phase 1 — Detect and prove commands
For each command the profile records, run it once and record the actual observed behavior. Never write a command you have not proven.
ZFA_OK projects — record the zfa engine
| Profile key | Command to prove |
|---|---|
| single_test | zfa tdd verify-red <behavior> --feature <f> (certifies one test red) |
| full_suite | flutter test (what zfa's gates invoke under the hood) |
| build | zfa build |
| loop | zfa tdd run <feature> --timeout 25 |
| verify | zfa tdd verify --feature <feature> |
Prove each: run zfa tdd init (idempotent baseline), zfa build (codegen
works), flutter test (day-zero suite green).
ZFA_MISSING projects — detect the raw stack
Detect framework (flutter/dart), test runner (flutter_test/test), mutation tool (mutation_test), coverage tool. Prove each command.
Phase 2 — Write the profile
Write .specify/memory/tdd-profile.md:
# Stack Profile
Detected: <date>
Engine: zfa (zuraffa-wired) | raw (non-zuraffa)
## Commands (proven)
- single_test: <command>
- full_suite: <command>
- build: <command>
- loop: <command>
- verify: <command>
## Notes
<anything special about this stack>
Phase 3 — Sanity check
Run the full suite once more from the profile's recorded command. It must be green (or document why not).
Phase 4 — Constitution principle
Unless --no-constitution: ensure the TDD principle is in the constitution:
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.
- 4d ago Changed · +91 lines · +37 tokens per session 71ee7a59077b
- 6d ago Changed · -209 lines · -55 tokens per session scan B → A b46b8cc646f4
- 10d ago First seen · 210 lines · 55 tokens per session scan B ef5bcae17506
speckit-tdd-setup is a skill published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 710 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-31.
Other skills, from other repositories
compose:tdd
Use when implementing any feature or bugfix, before writing implementation code.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.
tdd-cycle
Execute full TDD red-green-refactor cycle with validation gates. Use when saying "TDD cycle", "test-driven development", or "full TDD workflow".
common-tdd
Guides quality-first TDD for new behavior, bug fixes, and test changes. Selects the smallest test layer, proves a distinct regression risk, and runs bounded RED-GREEN-REFACTOR verification.
implement
Implement a technical design by decomposing it into dependency-ordered vertical slices, executing each with TDD red-green, reviewing each via an isolated sub-agent, and persisting progress to a state file so work survives session restarts. Use when the user has a tech design (doc or settled conversation) and says…