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/yugasun/aiops/tddnpx skills add yugasun/aiops --skill tddgit clone --depth 1 https://github.com/yugasun/aiopsWrote 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/yugasun/aiops/tdd)<a href="https://agentmods.dev/skills/yugasun/aiops/tdd"><img src="https://agentmods.dev/badge/skills/yugasun/aiops/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.00017 | $0.00215 |
| Opus 5 | $0.00009 | $0.00108 |
| Sonnet 5 | $0.00003 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00021 |
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 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
TDD
Tests verify behavior through public interfaces, not implementation. Good tests survive refactors; bad tests break on rename.
See tests.md and mocking.md for examples.
Anti-pattern: horizontal slices
Don't write all tests then all code. One behavior: RED → GREEN → repeat.
Workflow
- Plan — read
CONTEXT.md/ADRs. Confirm interface changes and behaviors to test with user. - Tracer bullet — one test, one minimal implementation, passes.
- Loop — one test at a time; only code to pass current test; no speculation.
- Refactor — only when GREEN; see refactoring.md.
Per-cycle checklist
- Describes behavior, not implementation
- Uses public interface only
- Minimal code for this test
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 28 lines · 17 tokens per session scan A 5fa58d44a02f
tdd is a skill published in the GitHub repository yugasun/aiops (4 stars, last pushed 16d ago), licensed Apache-2.0. It adds 17 tokens to every session and 215 once invoked, about $0.0001 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
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
speq-implement
Orchestrate implementation of a reviewed plan: task breakdown, TDD sub-agents, code review, and verification report. Use when the user asks to implement, build, or execute a plan under specs/plans/ — after /speq-plan, before /speq-record. Arg: .
speq-code-guardrails
TDD cycle and code quality guardrails — failing-test-first, evidence, dependency, error-handling, and test-quality rules. Triggered by /speq-implement, implementer-agent, implementer-expert-agent, and code-reviewer before any implementation or review work.
cf-tdd
Use when writing new production code, adding features, implementing, or refactoring — e.g. "implement this", "build this feature", "create a function", "add a new endpoint", "write the implementation", "refactor this", "write a test", "add tests", "create a component", "implement the API", "add a route". Also…
hashiiiii-images
Use this skill to create project images, especially flat geometric images with a dark background and one accent color.
hashiiiii-pull-request
Use this skill to create or edit a GitHub pull request with the repository template or the default structure.