SpecPilot: Instructions file for Claude Code

CLAUDE.md

SpecPilot CLAUDE.md is an instructions file for Claude Code from girishr/SpecPilot. It costs 675 tokens per session, scanned A, original, MIT.

A Claude Code instruction file for SpecPilot, a TypeScript command-line tool that manages specifications and development tasks.

In plain words
What is it for?
Use it when working on SpecPilot projects that store requirements, plans, tasks, and development records in a .specs directory.
Why use it?
It sets rules for reading and updating project specifications before code changes and for avoiding unrequested commits, pushes, or releases.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/girishr/specpilot/claude-md.svg)](https://agentmods.dev/instructions/girishr/specpilot/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/girishr/specpilot/claude-md"><img src="https://agentmods.dev/badge/instructions/girishr/specpilot/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 675 This file is loaded in full into every session.
When invoked 675 The same file โ€” it is already loaded in full.
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.1 $0.00675 $0.00675
Opus 5 $0.00338 $0.00338
Sonnet 5 $0.00135 $0.00135
Haiku 4.5 $0.00068 $0.00068

Measured 6d ago against content hash 9950d3921275, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

SpecPilot CLAUDE.md 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.

CLAUDE.md ยท 71 lines

How it starts

The opening of the file, as written. The whole thing โ€” 71 lines โ€” stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md โ€” SpecPilot SDD CLI

Primary instructions file for Claude Code. Keep lean โ€” router to .specs/ files, not a dumping ground. Full project context: .specs/project/project.yaml.

Project

  • Name: SpecPilot SDD CLI
  • Stack: TypeScript / Node.js / Commander.js
  • Specs location: .specs/

๐Ÿ”ด Critical Mandates โ€” Never violate, no exceptions

  1. No commit unless asked.
  2. No push unless asked.
  3. No deploy/publish/release unless asked.
  4. No .specs/ structure changes โ€” content only.
  5. Update specs after change:
    • Trivial โ†’ planning/tasks.md
    • Feature โ†’ project/requirements.md + planning/tasks.md
    • Architectural โ†’ all affected files + CHANGELOG.md
  6. Never reference file contents without reading first. If unread, say so.
  7. Never write code or change files unless asked. Ask first.
  8. Spec-first gate (scale to task size):
    • Trivial โ†’ no gate
    • Feature โ†’ read 1โ€“2 relevant .specs/ files before coding
    • Architectural โ†’ update all affected specs, present Spec Report, wait for yes, proceed

๐ŸŸก Process Mandates

  • Spec-First: Update .specs/ before writing code.
  • Log all AI interactions in .specs/development/prompts.md with timestamps.
  • Document decisions in .specs/development/context.md.

Code Philosophy โ€” Write Only What Needed

  1. Need exist? No โ†’ skip. Say why.
  2. Already in codebase? โ†’ reuse. Not rewrite.
  3. Stdlib do it? โ†’ use it.
  4. Native or installed dep cover it? โ†’ use. No new deps.
  5. One line do it? โ†’ write that.
  6. Only then: minimum code that work.
  7. Never cut: validation, error handling, security, explicit requirement.

Code Rules

  1. No abstraction, interface, factory, or pattern unless asked.
  2. No scaffold "for later". Later scaffold itself.
  3. Delete before add.
  4. Shortest correct diff win.
  5. Fix cause, not symptom. One guard in shared function beat guard in every caller.
  6. Boring over clever. Clever = 3am bug.
  7. Read before write. Never reference code you haven't read.

Read the full file on GitHub ยท 71 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. 6d ago First seen ยท 71 lines ยท 675 tokens per session scan A 9950d3921275

Subscribe to this mod's changes

SpecPilot CLAUDE.md is an instructions file published in the GitHub repository girishr/SpecPilot (37 stars, last pushed 1mo ago), licensed MIT. It adds 675 tokens to every session, about $0.0034 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.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js ยท 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex ยท 5,182 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode ยท 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode ยท 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain ยท 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart โ€” add a new integration in 5 steps, integration architecture and integrationmanifest โ€” file tracking.

github/spec-kit ยท 7,104 tokens