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-glossary-contextgit 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-glossary-context)<a href="https://agentmods.dev/skills/priivacy-ai/spec-kitty/spec-kitty-glossary-context"><img src="https://agentmods.dev/badge/skills/priivacy-ai/spec-kitty/spec-kitty-glossary-context/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-glossary-context"><img src="https://agentmods.dev/badge/skills/priivacy-ai/spec-kitty/spec-kitty-glossary-context.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.00083 | $0.02464 |
| Opus 5.5 | $0.00033 | $0.00986 |
| Sonnet 5.5 | $0.00017 | $0.00493 |
| Haiku 4.5 | $0.00008 | $0.00246 |
Grade A, and why
spec-kitty-glossary-context 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 2mo 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec-kitty-glossary-context
Maintain semantic integrity by curating the project glossary, detecting term drift, and ensuring that all mission artifacts use canonical terminology.
Use this skill when the user wants to inspect, update, or enforce glossary terms. Do not use it for purely operational tasks like advancing the runtime loop or repairing an installation.
How the Glossary Works
The glossary is a semantic integrity runtime — a 5-layer middleware pipeline that intercepts mission step execution, extracts terms from inputs/outputs, checks them against stored definitions, and can block generation if terminology conflicts are unresolved.
Data Model
Terms have a surface (normalized to lowercase), definition, scope,
confidence (0.0–1.0), and status (draft/active/deprecated).
Seed files (.kittify/glossaries/{scope}.yaml) provide initial definitions.
Event logs (.kittify/events/glossary/*.events.jsonl) record all runtime
mutations as append-only JSONL. State is reconstructed by replaying seed files
then events.
4 Scopes (narrowest wins)
| Precedence | Scope | Use For |
|---|---|---|
| 0 (highest) | mission_local |
Feature-specific jargon |
| 1 | team_domain |
Team/org conventions |
| 2 | audience_domain |
Industry/domain standards |
| 3 (lowest) | spec_kitty_core |
Framework terms (lane, work package, mission) |
The 5-Layer Middleware Pipeline
When a mission primitive executes (via @glossary_enabled decorator or
GlossaryAwarePrimitiveRunner), this pipeline processes the step:
Layer 1 — Term Extraction. Scans step input/output for terminology using multiple methods (in priority order):
| Method | Confidence | Example |
|---|---|---|
Metadata hints (glossary_watch_terms) |
1.0 | Explicit list of terms to monitor |
| Quoted phrases | 0.8 | "work package" in text |
| Acronyms (2-5 uppercase) | 0.8 | WP, API |
| Casing patterns (snake_case, CamelCase) | 0.8 | worktree_node, WorkspaceManager |
| Repeated nouns (3+ occurrences) | 0.5 | Frequent domain words |
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.
- 2mo ago First seen · 297 lines · 83 tokens per session scan A e9592a088d2d
spec-kitty-glossary-context is a skill published in the GitHub repository Priivacy-ai/spec-kitty (1,687 stars, last pushed 12d ago), licensed MIT. It adds 83 tokens to every session and 2,464 once invoked, about $0.0003 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
evidence-led-authoring
Shared bootstrap-owner contract for evidence-backed brownfield candidates, provenance, and imported baseline coverage.
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
spring-boot-4-conventions
Spring Framework 7 / Spring Boot 4 idioms and defaults. Use when writing or reviewing controllers, services, configuration, HTTP clients, async/virtual-thread code, or anything touching Spring's programming model.
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.
junit5-testcontainers-patterns
JUnit 5 + Spring Boot 4 test slice patterns and Testcontainers integration test patterns with @ServiceConnection. Use when writing or reviewing any test, especially when choosing between unit / slice / integration scope.
ears-spec-authoring
Author acceptance criteria using EARS-lite shapes with stable AC-NNN IDs and explicit Q-NNN open questions. Use when drafting or editing 01-spec.md, when transforming a tracker ticket into ACs, or when a user asks for a spec / requirements doc.