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.
curl -O https://raw.githubusercontent.com/girishr/SpecPilot/main/CLAUDE.mdgit clone --depth 1 https://github.com/girishr/SpecPilotWrote 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/instructions/girishr/specpilot/claude-md)<a href="https://agentmods.dev/instructions/girishr/specpilot/claude-md"><img src="https://agentmods.dev/badge/instructions/girishr/specpilot/claude-md/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.
<a href="https://agentmods.dev/instructions/girishr/specpilot/claude-md"><img src="https://agentmods.dev/badge/instructions/girishr/specpilot/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00847 | $0.00847 |
| Opus 5.5 | $0.00339 | $0.00339 |
| Sonnet 5.5 | $0.00169 | $0.00169 |
| Haiku 4.5 | $0.00085 | $0.00085 |
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 4d 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 — 72 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
- No commit unless asked.
- No push unless asked.
- No deploy/publish/release unless asked.
- No
.specs/structure changes — content only. - Update specs after change:
- Trivial →
planning/tasks.md - Feature →
project/requirements.md+planning/tasks.md - Architectural → all affected files +
CHANGELOG.md
- Trivial →
- Never reference file contents without reading first. If unread, say so.
- Never write code or change files unless asked. Ask first.
- 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.mdwith timestamps. - Document decisions in
.specs/development/context.md. - Tasks: When the SpecPilot MCP tools are connected, use them to add and move tasks. Otherwise edit
.specs/planning/tasks.mddirectly and keep its table format:| ID | Type | Priority | Description |under## Backlog,## Current Sprintand## Review(Typefeat,bugorchore, PriorityP1,P2orP3, either may be empty; a table there that is| ID | Description |keeps that shape),| # | ID | Description |under## Completed, one row per task. Finished work goes from Current Sprint to Review, never straight to Completed; a Review row gets its Completed entry (number, CD ID, commit) only once it ends withApproved <date>.
Code Philosophy — Write Only What Needed
- Need exist? No → skip. Say why.
- Already in codebase? → reuse. Not rewrite.
- Stdlib do it? → use it.
- Native or installed dep cover it? → use. No new deps.
- One line do it? → write that.
- Only then: minimum code that work.
- Never cut: validation, error handling, security, explicit requirement.
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.
- 4d ago Changed · +94 tokens per session 72c23977d1ae
- 8d ago Changed · +40 tokens per session 3ebcca88ec47
- 16d ago Changed · +1 lines · +38 tokens per session 82863f41775b
- 2mo ago First seen · 71 lines · 675 tokens per session scan A 9950d3921275
SpecPilot CLAUDE.md is an instructions file published in the GitHub repository girishr/SpecPilot (39 stars, last pushed today), licensed MIT. It adds 847 tokens to every session, about $0.0034 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.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.