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.svg" alt="Measured on agentmods" 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.00675 | $0.00675 |
| Opus 5 | $0.00338 | $0.00338 |
| Sonnet 5 | $0.00135 | $0.00135 |
| Haiku 4.5 | $0.00068 | $0.00068 |
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.
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
- 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.
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.
Code Rules
- No abstraction, interface, factory, or pattern unless asked.
- No scaffold "for later". Later scaffold itself.
- Delete before add.
- Shortest correct diff win.
- Fix cause, not symptom. One guard in shared function beat guard in every caller.
- Boring over clever. Clever = 3am bug.
- Read before write. Never reference code you haven't read.
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.
- 6d 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 (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.
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.
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.
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).
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).
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.
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.