Borrowing it
Nothing to install: this file belongs to alfredoperez/speckit-companion. 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/alfredoperez/speckit-companion/main/CLAUDE.mdgit clone --depth 1 https://github.com/alfredoperez/speckit-companionWrote 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/alfredoperez/speckit-companion/claude-md)<a href="https://agentmods.dev/instructions/alfredoperez/speckit-companion/claude-md"><img src="https://agentmods.dev/badge/instructions/alfredoperez/speckit-companion/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/alfredoperez/speckit-companion/claude-md"><img src="https://agentmods.dev/badge/instructions/alfredoperez/speckit-companion/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.01429 | $0.01429 |
| Opus 5 | $0.00714 | $0.00714 |
| Sonnet 5 | $0.00286 | $0.00286 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
speckit-companion 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
SpecKit Companion is a VS Code extension that gives AI assistants (terminal CLIs, IDE chat, the Claude Code panel) visual spec-driven development: specs (spec/plan/tasks), steering docs, and the Companion pipeline. The repo also ships a second, independently-versioned spec-kit extension under speckit-extension/. Provider list: README "Supported AI Providers".
Where things are documented
Read the matching doc instead of re-deriving from code:
docs/doc-sync.md— docs are part of the change, not a follow-up. Which doc each area maps to, the feature → README section map, the per-release checklist, changelog voice. Consult before finishing any user-facing change.docs/architecture.md— structure and module map.docs/capture-and-timing.md+docs/spec-context-schema.md— how.spec-context.jsongets captured, and its schema (read-then-merge writes;transitions[]is append-only).docs/viewer-states.md,docs/sidebar.md,docs/template-profiles.md— viewer state machine, sidebar reference, pipeline/workflow presets.docs/visual-assets.md: how docs images and README GIFs are made and when to regenerate them. Everything indocs/screenshots/generated/is a build artifact ofscripts/capture-docs-images.mjs(Storybook capture stories + Teamboard fixtures); the GIFs render frommedia/feature-clips/compositions. Any webview UI, styling, token, or fixture change makes them stale: regenerate, never hand-edit..claude/review-checklist.md— webview/CSS correctness invariants review scans for (.sr-onlyvshidden, ellipsis trio, Preact string styles, etc.).speckit-extension/docs/publishing.md— spec-kit extension release flow.
Gotchas
Two extensions, two sets of docs
The two extensions each have their own README, CHANGELOG, version, release flow, and tag namespace: VS Code extension = root README.md/CHANGELOG.md, package.json version, /publish → v* tag; spec-kit extension = speckit-extension/README.md/CHANGELOG.md, extension.yml extension.version, /publish-speckit-ext → speckit-ext-v* tag (/publish-both runs both). A change under speckit-extension/ updates its docs, never the root ones (and vice-versa); overlapping entries for a feature spanning both halves are expected. Never edit .specify/extensions/companion/CHANGELOG.md — generated, gitignored, overwritten on install. The release flow owns the version bump — feature branches do not. A branch touching speckit-extension/ writes under ## [Unreleased] and leaves extension.yml version, the README badge, and publishing.md alone; bumping on a branch is what produces version/changelog/badge drift.
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 Changed · +42 tokens per session 78f11735f529
- 12d ago First seen · 55 lines · 1,387 tokens per session scan A afb3cd560866
speckit-companion CLAUDE.md is an instructions file published in the GitHub repository alfredoperez/speckit-companion (90 stars, last pushed yesterday), licensed MIT. It adds 1,429 tokens to every session, about $0.0071 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).
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.
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 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).