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/oreum-ai/smartstack/tddnpx skills add oreum-ai/smartstack --skill tddgit clone --depth 1 https://github.com/oreum-ai/smartstackWhat 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.00375 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 31 lines · 0 tokens per session scan A 90f5b9cfdc5a
tdd is a skill published in the GitHub repository oreum-ai/smartstack (5 stars, last pushed 3mo 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…