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 kxdds/sdd-tdd --skill bootstrap-sdd-tddgit clone --depth 1 https://github.com/kxdds/sdd-tddWrote 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/kxdds/sdd-tdd/bootstrap-sdd-tdd)<a href="https://agentmods.dev/skills/kxdds/sdd-tdd/bootstrap-sdd-tdd"><img src="https://agentmods.dev/badge/skills/kxdds/sdd-tdd/bootstrap-sdd-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.1 | $0.00072 | $0.03373 |
| Opus 5 | $0.00036 | $0.01687 |
| Sonnet 5 | $0.00014 | $0.00675 |
| Haiku 4.5 | $0.00007 | $0.00337 |
Grade A, and why
bootstrap-sdd-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 7d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap SDD-TDD (universal)
Build, validate, or remove the project-local OpenSpec + Superpowers workflow from any coding agent. Treat setup as idempotent: preserve valid existing work and repair only missing or incompatible framework files.
Commands
bootstrap-sdd-tdd setup(default when no command is given): check dependencies, install with user consent, scaffold the sdd-tdd schema, and place theopenspec-superpowersbridge skill in the host tool's skills directory.bootstrap-sdd-tdd clean: remove everything this skill generated and restore OpenSpec to its default orchestration. Never uninstalls the OpenSpec CLI or the Superpowers plugin, and never deletes this bootstrap skill itself.
Step 0: Detect the host tool
Determine which agent tool you are running inside. Use, in order:
- Your own knowledge of your identity (you usually know which product you are).
- Directory markers in the project and environment:
.codex/,.claude/,.cursor/,.opencode/,.agents/,.gemini/. - If still ambiguous, ask the user one concise question.
Then resolve two lookups from the tables below: (a) where the bridge skill goes, (b) how Superpowers is installed.
Table A -- bridge skill target directory
Rule: if the host tool has its own project-local skills directory, use it; otherwise use the cross-tool generic .agents/skills/.
| Host tool | Bridge skill location | Extra packaging |
|---|---|---|
| Codex | .codex/skills/openspec-superpowers/SKILL.md |
Also write agents/openai.yaml next to it (interface metadata) |
| Claude Code | .claude/skills/openspec-superpowers/SKILL.md |
none |
| Cursor | .cursor/skills/openspec-superpowers/SKILL.md |
none |
| Antigravity (IDE/CLI) | .agents/skills/openspec-superpowers/SKILL.md |
Ensure root AGENTS.md mentions the skill so it is discoverable |
| OpenCode | .opencode/skills/openspec-superpowers/SKILL.md |
none |
| Gemini CLI | .gemini/skills/openspec-superpowers/SKILL.md |
none |
| Unknown / other | .agents/skills/openspec-superpowers/SKILL.md |
Ensure root AGENTS.md mentions the skill |
What ships with it
2 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.
- 7d ago First seen · 190 lines · 72 tokens per session scan A ebe92dce6247
bootstrap-sdd-tdd is a skill published in the GitHub repository kxdds/sdd-tdd (1 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 3,373 once invoked, about $0.0004 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
agentic-code-review
Use when reviewing a diff, pull request, branch, or AI-generated code for correctness, security, regression, test, performance, and maintainability risks before merge.
hooksmith
Use when designing or reviewing safe Grok Build hooks for linting, tests, formatting, notifications, command guards, lifecycle automation, or project hook trust decisions.
repo-health-check
Use when auditing a repo before changes to find the smallest safe PR, quality risks, stale docs, missing tests, ignored-file gaps, or agent setup issues. Best first skill for unfamiliar codebases.
architecture-review
Use for clean architecture, modular monoliths, hexagonal boundaries, service boundaries, data flow, dependency direction, ADRs, or large feature planning.
frontend-ux-engineer
Use for frontend features, Next.js/React/Vue/Svelte UI, accessibility, responsive layout, design polish, state handling, forms, visual QA, or product workflow improvements.
git-github-flow
Use for branch prep, clean commits, PR descriptions, GitHub issue triage, changelogs, release notes, review response, merge readiness, or publishing a branch safely.