agentmods.dev

specify

specify is a command for Claude Code from ThibautBaissac/rails_ai_agents. It costs 19 tokens per session (859 once invoked), scanned A, original, MIT.

A command that creates a short change specification for a small bug fix or feature instead of using a full software design process.

In plain words
What is it for?
Use it to start small changes with an automatically chosen branch name and the repository's configured numbering scheme.
Why use it?
It turns a brief change description into a named feature branch and a concise plan, reducing setup work for limited changes.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

not rated 672repo +1 5mo ago A scan 19 tokens original MIT

Good fit Use it to start small changes with an automatically chosen branch name and the repository's configured numbering scheme.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/thibautbaissac/rails_ai_agents/specify
View source ↗ ThibautBaissac/rails_ai_agents thibautbaissac.github.io
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.

Clone the repo
git clone --depth 1 https://github.com/ThibautBaissac/rails_ai_agents

Made for: Claude Code.

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 specify

README.md
[![agentmods](https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/specify/github.svg)](https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/specify)
Your own site
<a href="https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/specify"><img src="https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/specify/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.

agentmods 80×15 button for specify

Your own site · 80×15
<a href="https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/specify"><img src="https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/specify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 859 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00019 $0.00859
Opus 5.5 $0.00008 $0.00344
Sonnet 5.5 $0.00004 $0.00172
Haiku 4.5 $0.00002 $0.00086

Measured 2mo ago against content hash 3f4b8a5b47a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

.claude/commands/sdd-change/specify.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 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 /sdd-change:specify in the triggering message is the change description. Do not ask the user to repeat it unless they provided an empty command.

Given that change description, do this:

  1. Generate a concise short name (2-4 words) for the branch:

    • Analyze the description and extract the most meaningful keywords
    • Use action-noun format (e.g., "fix-login-timeout", "add-csv-export", "update-email-template")
    • Preserve technical terms and acronyms

  2. Create the feature branch by running the script:

    Branch numbering mode: Check if .specify/init-options.json exists and read the branch_numbering value.

    • If "timestamp", add --timestamp to the script invocation
    • If "sequential" or absent, do not add any extra flag

    Run: .specify/scripts/bash/create-new-feature.sh "$ARGUMENTS" --json --short-name "<name>" "<description>"

    IMPORTANT:

    • Do NOT pass --number — the script determines the next number automatically
    • Always include --json so the output can be parsed reliably
    • You must only ever run this script once per change
    • Parse the JSON output for BRANCH_NAME and SPEC_FILE paths
    • For single quotes in args, use escape syntax: e.g 'I'''m Groot' (or double-quote if possible)

  3. Load the change-spec template: Read .specify/templates/change-spec-template.md for the required structure.

  4. Load constitution (if exists): Read .specify/memory/constitution.md to respect project principles when filling the spec.

  5. Fill the change spec and overwrite SPEC_FILE with content based on the change-spec-template structure:

    • Problem: 2-3 sentences describing current vs expected behavior. Be specific.
    • Proposed Change: What the fix/change looks like from the user's perspective. No implementation details.
    • Acceptance Criteria: 1-3 Given/When/Then scenarios. Keep it focused and testable.
    • Files Likely Affected: Analyze the codebase to identify specific file paths. Use Glob/Grep if needed.
    • Assumptions: Document any best-guess decisions. NO [NEEDS CLARIFICATION] markers — make reasonable assumptions and document them here.
    • Type: Classify as Bug Fix, Small Feature, or Refactor.

Read the full file on GitHub · 76 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. 2mo ago First seen · 76 lines · 19 tokens per session scan A 3f4b8a5b47a2

Subscribe to this mod's changes

specify is a command published in the GitHub repository ThibautBaissac/rails_ai_agents (672 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 859 once invoked, about $0.0001 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.

Planning
Related

specify compared with commands from other repositories

specify next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
specifyThibautBaissac/rails_ai_agentsCommand6725mo agoMITA19Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code