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 oreum-ai/smartstack --skill tddgit clone --depth 1 https://github.com/oreum-ai/smartstackWrote 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/oreum-ai/smartstack/tdd)<a href="https://agentmods.dev/skills/oreum-ai/smartstack/tdd"><img src="https://agentmods.dev/badge/skills/oreum-ai/smartstack/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/oreum-ai/smartstack/tdd"><img src="https://agentmods.dev/badge/skills/oreum-ai/smartstack/tdd.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.00000 | $0.00375 |
| Opus 5.5 | $0.00000 | $0.00150 |
| Sonnet 5.5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
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 2mo 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
Skill: TDD (Test-Driven Development)
When to use
Before writing any high-risk logic: authentication, authorization, money/billing, core domain rules, data integrity, anything irreversible. Required there because a silent bug is dangerous or expensive.
The cycle: Red → Green → Refactor
- Red — write a failing test first. State the expected behavior as a test before the code exists. Name it like a sentence. Run it; watch it fail. A test that passes before you write the code tests nothing.
- Green — write the minimum code to pass. Don't gold-plate; just make it green.
- Refactor — clean it up with the test as a safety net. Improve names/structure; the test proves you didn't change behavior.
- Repeat for the next behavior / the next failure path.
What to cover before moving on
- The happy path (valid input → expected result).
- Every failure path (invalid input, missing data, unauthorized, boundary values).
Rules
- One behavior per test; deterministic; independent (no shared mutable state, no order dependence).
- Test the contract (inputs → outputs/side-effects), not internal implementation.
- For data logic, use fakes/mocks or a disposable test database — never prod data.
- A red test blocks the ship. Never comment out a failing test to "make it pass."
Procedure with your AI assistant
- Read
rules/testing.mdand the relevantcontext/file. - Write the failing test(s) for the next behavior; confirm they fail for the right reason.
- Implement the minimum code; run until green.
- Refactor; keep green.
- Record any bug found along the way in the error ledger.
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.
- 2mo ago First seen · 31 lines · 0 tokens per session scan A 90f5b9cfdc5a
tdd is a skill published in the GitHub repository oreum-ai/smartstack (6 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 375 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-31.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.