SpecPilot: Command for Claude Code

.claude/commands/specpilot-refine.md

specpilot-refine is a command for Claude Code from girishr/SpecPilot. It costs 19 tokens per session (189 once invoked), scanned A, original, MIT.

A command that proposes changes to a project's requirements documents from a new requirement description and shows a line-by-line preview before writing.

In plain words
What is it for?
Use it to refine requirements, development context, and prompts while keeping stable requirement IDs such as REQ-002.A.6.
Why use it?
It makes requirement updates reviewable and waits for confirmation, helping prevent accidental or unclear changes to project specifications.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

This is girishr/SpecPilot's own configuration. It tells Claude Code how to work on SpecPilot itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything SpecPilot configures →

Reuse

Borrowing it

Nothing to install: this file belongs to girishr/SpecPilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/girishr/SpecPilot/main/.claude/commands/specpilot-refine.md
Clone the repo
git clone --depth 1 https://github.com/girishr/SpecPilot

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 specpilot-refine

README.md
[![agentmods](https://agentmods.dev/badge/commands/girishr/specpilot/specpilot-refine.svg)](https://agentmods.dev/commands/girishr/specpilot/specpilot-refine)
Your own site
<a href="https://agentmods.dev/commands/girishr/specpilot/specpilot-refine"><img src="https://agentmods.dev/badge/commands/girishr/specpilot/specpilot-refine.svg" alt="Measured on agentmods" 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 189 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.00189
Opus 5 $0.00010 $0.00095
Sonnet 5 $0.00004 $0.00038
Haiku 4.5 $0.00002 $0.00019

Measured 8d ago against content hash acd266d3c551, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

specpilot-refine 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 8d 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/specpilot-refine.md · 16 lines

What it actually says

Refine the project's spec files with a new requirement.

Requirement description: $ARGUMENTS

  1. Read the current .specs/project/requirements.md, .specs/development/context.md, and .specs/development/prompts.md.
  2. Propose specific additions or edits to those files that incorporate the requirement description above, following the existing stable-ID conventions (e.g. REQ-###.#).
  3. Show a line-level diff preview of every proposed change — do not just describe it.
  4. Wait for the user's confirmation before writing anything.
  5. Once confirmed, write the changes.

This mirrors the CLI's specpilot refine (REQ-002.A.6) as a standalone agent workflow — it has no dependency on the CLI being installed.

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. 8d ago First seen · 16 lines · 19 tokens per session scan A acd266d3c551

Subscribe to this mod's changes

specpilot-refine is a command published in the GitHub repository girishr/SpecPilot (37 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 189 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.