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/caipe-io/ai-platform-engineering/speckit.specifygit clone --depth 1 https://github.com/caipe-io/ai-platform-engineeringWrote 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/commands/caipe-io/ai-platform-engineering/speckit.specify)<a href="https://agentmods.dev/commands/caipe-io/ai-platform-engineering/speckit.specify"><img src="https://agentmods.dev/badge/commands/caipe-io/ai-platform-engineering/speckit.specify.svg" alt="Measured on agentmods" height="20"></a>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.00013 | $0.03135 |
| Opus 5 | $0.00006 | $0.01568 |
| Sonnet 5 | $0.00003 | $0.00627 |
| Haiku 4.5 | $0.00001 | $0.00314 |
Grade A, and why
speckit.specify 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 6d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
The text the user typed after /speckit.specify in the triggering message is the feature description. Assume you always have it available in this conversation even if $ARGUMENTS appears literally below. Do not ask the user to repeat it unless they provided an empty command.
Given that feature description, do this:
-
Generate a concise short name (2-4 words) for the branch:
- Analyze the feature description and extract the most meaningful keywords
- Create a 2-4 word short name that captures the essence of the feature
- Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
- Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
- Keep it concise but descriptive enough to understand the feature at a glance
- Examples:
- "I want to add user authentication" → "user-auth"
- "Implement OAuth2 integration for the API" → "oauth2-api-integration"
- "Create a dashboard for analytics" → "analytics-dashboard"
- "Fix payment processing timeout bug" → "fix-payment-timeout"
-
Confirm branch creation with the user BEFORE running the script. The script's default behaviour is to
git checkout -b <new-branch>, which is destructive (it changes the user's checked-out branch and leaves any uncommitted spec edits on a fresh branch the user did not consent to). Some maintainers want a new branch every time; others prefer to keep spec work on the current branch and bundle it with other in-flight changes.- Show the user the proposed branch name (e.g.
2026-05-07-user-auth) and ask whether to create it. - Phrasing:
"I'll create a new branch named '<proposed-branch-name>' for this spec. Reply 'no branch' (or 'stay on current branch') if you'd rather keep spec edits on '<current-branch>'." - Default if the user does not respond / responds ambiguously: create the branch (matches today's behaviour). But if the user has already said something like "don't create a new branch" earlier in the session — honour that without re-asking.
- If the user declines, pass
--no-branchto the script in the next step. The script will still create the spec folder underdocs/docs/specs/<branch-name>/and writespec.md; only thegit checkout -bis skipped.
- Show the user the proposed branch name (e.g.
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.
- 6d ago First seen · 247 lines · 13 tokens per session scan A 6a711f509eea
speckit.specify is a command published in the GitHub repository caipe-io/ai-platform-engineering (406 stars, last pushed yesterday), licensed Apache-2.0. It adds 13 tokens to every session and 3,135 once invoked, about $0.0001 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 commands, from other repositories
service-check
Request each agent to run a self-diagnostic to validate their runtime setup.
compatibility-audit
Audit all agents for Trinity compatibility by requesting self-diagnostics from each agent.
schedules
Quick overview of all schedules across the platform.
stop
Command "stop" from Abilityai/trinity, covering stop agent, usage, instructions, agent stop: {agent-name} and safety checks.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.