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 commands/kaze-jp/kusa/spec-implgit clone --depth 1 https://github.com/kaze-jp/kusaWhat 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.00803 |
| Opus 5 | $0.00000 | $0.00402 |
| Sonnet 5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
spec-impl 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 2d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start Implementation
Begin implementing approved tasks using TDD in an isolated worktree. This is the manual implementation command — for fully autonomous execution (implementation → PR → review → merge), use /kiro:ao-run instead.
Usage
/kiro:spec-impl <feature-name> [task-numbers]
/kiro:spec-impl my-feature— all pending tasks/kiro:spec-impl my-feature 1.1— single task/kiro:spec-impl my-feature 1,2,3— specific tasks
Instructions
-
Validate prerequisites:
.kiro/specs/$FEATURE_NAME/tasks.mdmust exist. If not →/kiro:spec-tasksfirst..kiro/specs/$FEATURE_NAME/design.mdmust exist..kiro/specs/$FEATURE_NAME/requirements.mdmust exist.
-
Read context:
.kiro/specs/$FEATURE_NAME/tasks.md— task definitions, dependencies,(P)markers.kiro/specs/$FEATURE_NAME/design.md— API contracts, data models, component design.ao/steering/tech.md— coding standards, patterns.ao/steering/structure.md— file placement conventions.ao/ao.yaml— quality gate commands, git strategy
-
Create worktree:
- Use
/superpowers:using-git-worktreesto create an isolated worktree - Branch:
<git.branch_prefix><feature-name> - All implementation happens in the worktree — never on the base branch
- Use
-
Select tasks:
- If task numbers specified → execute those tasks only
- Otherwise → execute all pending tasks (
- [ ]in tasks.md) - Skip already completed tasks (
- [x]) - Respect dependency ordering
-
Execute each task with TDD (invoke
/superpowers:test-driven-development):For each task, follow Kent Beck's TDD cycle:
- RED: Write a failing test that captures the acceptance criteria
- GREEN: Write the minimum code to make the test pass
- REFACTOR: Clean up while keeping tests green
- VERIFY: Run quality gates from
ao.yaml(typecheck, lint, test, build) - MARK: Update
tasks.mdcheckbox from- [ ]to- [x]
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.
- 2d ago First seen · 76 lines · 0 tokens per session scan A 9e87c566b6da
spec-impl is a command published in the GitHub repository kaze-jp/kusa (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 803 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 commands, from other repositories
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
go-test
Go TDD workflow with table-driven tests.
pm-auto-design2dev
設計レビューから実装完了まで完全自動化（設計レビュー→作業計画→TDD実装）.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
execute-plan
Execute an implementation plan methodically with TDD and continuous validation.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.