Borrowing it
Nothing to install: this file belongs to bonnguyenitc/specship. 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/bonnguyenitc/specship/main/CLAUDE.mdgit clone --depth 1 https://github.com/bonnguyenitc/specshipWrote 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/bonnguyenitc/specship/claude-md)<a href="https://agentmods.dev/instructions/bonnguyenitc/specship/claude-md"><img src="https://agentmods.dev/badge/instructions/bonnguyenitc/specship/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/bonnguyenitc/specship/claude-md"><img src="https://agentmods.dev/badge/instructions/bonnguyenitc/specship/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.00643 | $0.00643 |
| Opus 5.5 | $0.00257 | $0.00257 |
| Sonnet 5.5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
specship 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 1mo 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specship — dev guide
npm package that installs a spec→plan→coding→review skills workflow into
projects (Claude Code, Codex, Cursor, Antigravity). Entry: bin/cli.js →
src/cli.js; install logic in src/init.js + src/targets.js; skill sources
in skills/; subagent definitions in agents/ (installed only for targets
declaring subagents in targets.js — today just Claude Code); per-agent
templates in .claude/, .codex/, .cursor/, .antigravity/.
Naming: ss- prefixes skills, never task state. Every skill folder and
frontmatter name: is ss-<skill> (skills/ss-spec/, /ss-ship), as are the
subagents in agents/ (ss-explorer, …). The pipeline's state vocabulary
stays bare: stage:, artifacts:, next_phase:, resume_phase:, --phase,
and the Pipeline Log's stage labels are all spec|plan|coding|review|debug|done.
Prefixing those would break every existing task.md. STAGE_SKILLS in
src/init.js is keyed by directory name, so it carries the prefix.
Verify every change
Always prove a change works before declaring it done:
npm test— zero-dep test suite (test/pipeline.test.js+test/cli.test.js). Fixtures must describe tasks that could actually exist: atask.mdwhoseartifacts:map names aconfirmedspec needsspec.mdon disk to match (use thefilesForhelper). Fictional fixtures hid a whole class of bugs once — seetasks/LESSONS.mdL2/L3.- Real install:
node bin/cli.js init --all --dir "$(mktemp -d)", then inspect the resulting tree (marker block in CLAUDE.md, skills copied, codex-onlyopenai.yamlmanifest, claude-only.claude/agents/subagents and nowhere else). - Anything touching packaging or
publish.sh:./publish.sh --dry-run.
Learnings
When Claude makes a mistake in this repo, don't just correct it in chat — add the lesson here as a bullet so it never repeats.
.claude/CLAUDE.mdis not only this repo's project instructions: it is the templatespecship initmerges into consumers' CLAUDE.md. Edits there ship to users — dev-only guidance belongs in this file (root CLAUDE.md).- package.json
filesmust list.claude/CLAUDE.md(the template), not the whole.claude/dir, so local dev config (settings.json,commands/) never ships in the npm tarball.
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.
- 1mo ago First seen · 44 lines · 643 tokens per session scan A e5812e593ec5
specship CLAUDE.md is an instructions file published in the GitHub repository bonnguyenitc/specship (2 stars, last pushed 2mo ago), licensed MIT. It adds 643 tokens to every session, about $0.0026 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-31.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.