agentmods.dev

speckit.specify

speckit.specify is an agent for coding agents from racecraft-lab/Paddock. It costs 13 tokens per session (2,612 once invoked), scanned A, original, MIT.

A command that turns a plain-language feature idea into a structured feature specification and prepares a branch for the work.

In plain words
What is it for?
Use it to capture feature requirements, choose a short branch name, and start work in a consistent development workflow.
Why use it?
It gives developers a shared description of what to build before implementation starts, reducing ambiguity and rework.

Agent

not rated 11 2mo ago A scan 13 tokens original MIT
View the source file racecraft-lab/Paddock
Install

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.

agentmods
npx agentmods add agents/racecraft-lab/paddock/speckit.specify
Clone the repo
git clone --depth 1 https://github.com/racecraft-lab/Paddock

Wrote 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.

agentmods badge for speckit.specify

README.md
[![agentmods](https://agentmods.dev/badge/agents/racecraft-lab/paddock/speckit.specify.svg)](https://agentmods.dev/agents/racecraft-lab/paddock/speckit.specify)
Your own site
<a href="https://agentmods.dev/agents/racecraft-lab/paddock/speckit.specify"><img src="https://agentmods.dev/badge/agents/racecraft-lab/paddock/speckit.specify.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,612 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.02612
Opus 5 $0.00006 $0.01306
Sonnet 5 $0.00003 $0.00522
Haiku 4.5 $0.00001 $0.00261

Measured yesterday against content hash dce638e0e921, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

.specify/extensions/verify-tasks/.github/agents/speckit.specify.agent.md · 240 lines

How it starts

The opening of the file, as written. The whole thing — 240 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:

  1. 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"

  2. Create the feature branch by running the script with --short-name (and --json), and do NOT pass --number (the script auto-detects the next globally available number across all branches and spec directories):

    • Bash example: .specify/scripts/bash/create-new-feature.sh "$ARGUMENTS" --json --short-name "user-auth" "Add user authentication"
    • PowerShell example: .specify/scripts/bash/create-new-feature.sh "$ARGUMENTS" -Json -ShortName "user-auth" "Add user authentication"

    IMPORTANT:

    • Do NOT pass --number — the script determines the correct next number automatically
    • Always include the JSON flag (--json for Bash, -Json for PowerShell) so the output can be parsed reliably
    • You must only ever run this script once per feature
    • The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for
    • The JSON output will contain BRANCH_NAME and SPEC_FILE paths
    • For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot")

Read the full file on GitHub · 240 lines

Changes

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.

  1. yesterday First seen · 240 lines · 13 tokens per session scan A dce638e0e921

Subscribe to this mod's changes

speckit.specify is an agent published in the GitHub repository racecraft-lab/Paddock (11 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 2,612 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-09-03.

Building agentsPlanningagent-orchestrationai-agentsgithub-issuesnextjssoftware-factorysqlite
Related

Other agents, from other repositories

merge-conflict-resolver

Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…

module-federation/core · 0 tokens

web-research-analyst

Web research: browser automation, Tavily API, competitive intelligence, documentation capture, technical recon.

yonatangross/orchestkit · 26 tokens

test-reporter

Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.

nrslib/takt · 0 tokens

ap-preflight-probe

L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.

Spielewoy/autoprompt-skill · 39 tokens

amp

Feature and research work are NOT complete until you run these commands yourself.

jayvee/aigon · 0 tokens

adapter_grok

Grok is an eagerly registered stock-TUI adapter. RimZ launches grok, installs passive global hooks in ${GROKHOME:-/.grok}/hooks/rimz.json, and enriches each session from its durable updates.jsonl, summary.json, signals.json, and optional events.jsonl files. ACP and provider-private billing APIs stay outside this…

rimio-ai/rimz · 0 tokens