Borrowing it
Nothing to install: this file belongs to joanseg/specmanager. 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/joanseg/specmanager/main/CLAUDE.mdgit clone --depth 1 https://github.com/joanseg/specmanagerWrote 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/joanseg/specmanager/claude-md)<a href="https://agentmods.dev/instructions/joanseg/specmanager/claude-md"><img src="https://agentmods.dev/badge/instructions/joanseg/specmanager/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/joanseg/specmanager/claude-md"><img src="https://agentmods.dev/badge/instructions/joanseg/specmanager/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.04834 | $0.04834 |
| Opus 5.5 | $0.01934 | $0.01934 |
| Sonnet 5.5 | $0.00967 | $0.00967 |
| Haiku 4.5 | $0.00483 | $0.00483 |
Grade A, and why
specmanager CLAUDE.md scanned grade A with 1 finding 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 14d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**A surface test is also required when the release changes packaging** — anything in `plugin.json` beyond the `version` bump, `.mcp.json`, `hooks/`, the plugin-root `package.json` / `package-lock.json`, `ui/vite.config.t How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project lifecycle (managed by SpecManager — do not edit by hand)
Specs live in .claude/specs/features/. Read the approved doc for a feature's stage before implementing it.
| Feature | Current stage | Notes |
|---|---|---|
| Redesign | PRD (approved) | — |
| Dummy feature | PRD | — |
| Post-phase design conformance check | PRD (draft) | — |
| Markdown viewer | PRD (approved) | — |
| Reinstall refactor | PRD (approved) | — |
| Interview command | PRD (approved) | — |
| Antigravity plugin | PRD (approved) | — |
| Share docs on public URL | PRD (approved) | — |
| Cursor plugin | PRD (approved) | — |
| Codex plugin | PRD (approved) | — |
| User adoption acceleration | PRD (draft) | — |
| Token usage optimisation | PRD (approved) | — |
| Viral loop feature | PRD (approved) | — |
| Feature demo recording | PRD | — |
| Spec-stage tier dispatch | PRD (approved) | — |
| GitHub spec sync (issues/PRs) | PRD | — |
| Security review stage | PRD (approved) | — |
| Multi-repo nested docs (CLAUDE.md / DESIGN.md) | PRD (approved) | — |
| Multi-session boards (auto-port) | PRD (approved) | — |
| Website agent readiness | PRD | — |
| Landing page redesign (ethskills style) | PRD (approved) | — |
| Marketing phase | PRD (approved) | Plan ⚠️ stale |
| Fly.io deployment | PRD (approved) | — |
| SpecManager simplification cleanup | PRD (approved) | — |
| Company-brain grounding | PRD | — |
| Cowork support | PRD (draft) | — |
10 features shipped — full history on the board.
Rules: don't start a feature's tasks until its Plan is approved; treat ⚠️ stale docs as needing reconciliation.
Commands:
/specmanager-prd · /specmanager-architecture · /specmanager-design (optional) · /specmanager-plan · /specmanager-build · /specmanager-walkthrough · /specmanager-board · /specmanager-interview (optional, pre-PRD)
Last synced: 2026-09-30T15:33:36.564Z
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
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.
- 14d ago Changed · +68 tokens per session a24c86ca5344
- 16d ago Changed · +18 lines · +491 tokens per session b04df9b7a81d
- 17d ago Changed · +12 lines · +1,000 tokens per session 70954212a80b
- 1mo ago First seen · 132 lines · 3,275 tokens per session scan A 820a17430233
specmanager CLAUDE.md is an instructions file published in the GitHub repository joanseg/specmanager (23 stars, last pushed 15d ago), licensed MIT. It adds 4,834 tokens to every session, about $0.0193 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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.
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.
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).