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-run-verdict-capturegit 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-run-verdict-capture)<a href="https://agentmods.dev/skills/priivacy-ai/spec-kitty/spk-run-verdict-capture"><img src="https://agentmods.dev/badge/skills/priivacy-ai/spec-kitty/spk-run-verdict-capture/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-run-verdict-capture"><img src="https://agentmods.dev/badge/skills/priivacy-ai/spec-kitty/spk-run-verdict-capture.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.00035 | $0.00659 |
| Opus 5 | $0.00017 | $0.00329 |
| Sonnet 5 | $0.00007 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
spk-run-verdict-capture 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 12d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spk-run-verdict-capture
Use this skill whenever an agent (any of the 13 slash-command harnesses or the shared Agent-Skill harnesses) needs to record the outcome of a WP review — approve, reject, or otherwise. It documents the single deterministic seam so verdicts never diverge by harness.
The authoritative seam
The sole authority for a WP's review verdict is the review_result event in the mission's
status.events.jsonl (read back via specify_cli.status.event_sourced_review_result). The
review-cycle-N.md render is non-authoritative prose — do not hand-edit it to change a
verdict, and never treat it as the source of truth. Because the verdict is an event, it is
append-only, deterministic, and identical across every agent.
How to set a verdict (use the CLI — do not write the event by hand)
- Approve a WP under review:
spec-kitty agent tasks move-task <WP> --to approved --mission <slug> --note "<why>" - Reject a WP (send it back with structured feedback):
spec-kitty agent tasks move-task <WP> --to planned \ --review-feedback-file <path/to/review-feedback-N.md> --mission <slug> - Terminal (done) with an explicit review triple (reviewer / verdict / reference):
spec-kitty agent status emit <WP> --to done --actor <name> \ --evidence-json '{"review": {"reviewer": "<name>", "verdict": "approved", "reference": "<PR/commit>"}}'
Each command emits the review_result (or review-bearing transition) event; the reduced snapshot
is what spec-kitty agent tasks status and merge preflight read.
Verdict vocabulary
The verdict field is validated against the canonical bridge specify_cli.status.event_verdicts()
plus the proof-event extras commented, rejected, unknown (see
specify_cli.proof.events). Do not invent verdict strings; an unknown verdict is rejected at the
seam. Moving a WP to done requires a review triple with reviewer, verdict, and reference.
Guardrails
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.
- 12d ago First seen · 55 lines · 35 tokens per session scan A e85e49b8077e
spk-run-verdict-capture is a skill published in the GitHub repository Priivacy-ai/spec-kitty (1,603 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 659 once invoked, about $0.0002 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…