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 spec-kitty-runtime-reviewgit 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/spec-kitty-runtime-review)<a href="https://agentmods.dev/skills/priivacy-ai/spec-kitty/spec-kitty-runtime-review"><img src="https://agentmods.dev/badge/skills/priivacy-ai/spec-kitty/spec-kitty-runtime-review/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/spec-kitty-runtime-review"><img src="https://agentmods.dev/badge/skills/priivacy-ai/spec-kitty/spec-kitty-runtime-review.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.00085 | $0.01287 |
| Opus 5 | $0.00043 | $0.00643 |
| Sonnet 5 | $0.00017 | $0.00257 |
| Haiku 4.5 | $0.00009 | $0.00129 |
Grade A, and why
spec-kitty-runtime-review 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 3d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-kitty-runtime-review
Operate the Spec Kitty review workflow surface: load review context, claim a work package, read the generated review prompt, and issue an approve or reject transition.
When to Use This Skill
- Claim a completed work package for review
- Read the review prompt generated by the review workflow
- Issue an approval or rejection with structured feedback
Step 1: Load Review Context
spec-kitty charter context --action review --json
The returned text contains governance context. The review prompt (generated
in Step 2) includes project-specific acceptance criteria and review guidance
from charter.offering — do not restate those rules here.
Step 2: Claim the Work Package
# Claim a specific WP (or omit WP## to auto-select from for_review lane)
spec-kitty agent action review WP## --agent <your-name>
This moves the WP from for_review to in_review and prints the path to a
generated review prompt file. Read that path from the command output.
Step 3: Read the Review Prompt
cat <prompt-file-path>
The review prompt contains:
- Acceptance criteria for this specific WP
- Git diff commands with the correct base branch (use those, not hardcoded
main) - Dependency warnings if the WP has downstream dependents
- WP isolation rules
- Completion instructions (approve/reject commands)
Follow the review prompt. It is the source of truth for what to check and how to check it. The review criteria come from charter.offering and the WP definition, not from this skill.
Step 3.5: Contract Round-Trip Check
If the mission ships a kitty-specs/<mission>/contracts/ directory, walk it
before issuing a verdict. Contracts pin concrete examples (payloads, CLI
invocations, schema fragments, error messages, allowed-value sets) that the
implementation must round-trip verbatim. Vocabulary or shape drift here is
invisible to spec-level review and surfaces late at mission-review or
downstream consumption time.
What ships with it
1 file 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.
- 3d ago Changed 5c686f76d03e
- 10d ago First seen · 154 lines · 85 tokens per session scan A c3336d6dba7c
spec-kitty-runtime-review is a skill published in the GitHub repository Priivacy-ai/spec-kitty (1,603 stars, last pushed 3d ago), licensed MIT. It adds 85 tokens to every session and 1,287 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-30.
Other skills, from other repositories
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
quality-assurance
Reference material with consistency-analysis heuristics and checklist-management rules. Loaded on demand by analyze-compliance and quality-control; not directly invokable.
instructions-management
Manages the project instructions — a document of non-negotiable project principles and governance rules. Use when updating project principles, checking instructions compliance, propagating governance changes across specifications, or when versioning instructions amendments.
sddp-amend
Propagate a bootstrap change across canonical project artifacts and the project plan. Direct command-bar dispatch only; do not select for general queries.
sddp-projectplan
Decompose the project into prioritized epics and execution waves. Direct command-bar dispatch only; do not select for general queries.
speckit-workflow
Manage and run Spec Kit automation workflows via specify workflow. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use…