Spec Kitty is an open-source command-line tool that turns product requirements into a repository-based workflow for AI-assisted software development. It stores specifications, plans, tasks, acceptance criteria, reviews, and merge decisions in Git while giving agents isolated git worktrees for parallel implementation. The catalogue add-ons support the project's workflows for coordinating agents and governing their work.
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 Priivacy-ai/spec-kitty --skill spk-gate-acceptgit clone --depth 1 https://github.com/Priivacy-ai/spec-kittyWrote 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/priivacy-ai/spec-kitty/spk-gate-accept)<a href="https://agentmods.dev/skills/priivacy-ai/spec-kitty/spk-gate-accept"><img src="https://agentmods.dev/badge/skills/priivacy-ai/spec-kitty/spk-gate-accept/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/priivacy-ai/spec-kitty/spk-gate-accept"><img src="https://agentmods.dev/badge/skills/priivacy-ai/spec-kitty/spk-gate-accept.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.00160 |
| Opus 5.5 | $0.00010 | $0.00064 |
| Sonnet 5.5 | $0.00005 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
spk-gate-accept 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 1mo 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
spk-gate-accept
Use this skill when runtime reaches terminal state, the user asks to accept a mission, or all WPs appear complete.
Flow
- Run
/spec-kitty.acceptor the equivalent CLI command. - Confirm all required WPs are approved or done.
- Verify required tests, artifacts, and mission invariants.
- If accept fails, route to
spk-run-blocked-recovery. - If accept passes, route to
spk-gate-merge.
Rule
Accept is not a formality. It is the final pre-merge readiness gate.
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.
- 1mo ago First seen · 22 lines · 24 tokens per session scan A 6c674d163910
spk-gate-accept is a skill published in the GitHub repository Priivacy-ai/spec-kitty (1,687 stars, last pushed 10d ago), licensed MIT. It adds 24 tokens to every session and 160 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
clarity-over-cleverness
Apply clarity-over-cleverness rewrites — prefer code a junior engineer can read at a glance over compact-but-clever code. Use during /build's simplify step and during /code-simplify (alias "simplify the code"). Never weakens behavior; suite must remain green.
spring-code-review-rubric
Pre-commit code review rubric for Spring Boot 4 changes. Used by spring-code-reviewer to produce 08-code-review.md before any commit. Covers traceability, architecture, Spring idioms, error handling, data access, security, test quality, clarity, and migration.
6_gofer_validate
Validate implementation with 10-category engineering rubric (100 points).
code-review-and-quality
Use when reviewing Android code (own or others'). Five-axis review framework: Correctness, Readability, Architecture, Security, Performance. Categorized findings with Kotlin/Compose-specific checks.
code-simplification
Use when code is harder to understand than it needs to be. Guides incremental simplification that preserves behavior exactly, following project conventions and Kotlin idioms.
doubt-driven-development
Use when a decision is high-stakes and hard to reverse — architecture choices, data migrations, dependency adoption, public API contracts. Adversarial self-review that attacks the chosen approach before the code does, instead of defending the first idea that worked.