Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/rhuss/cc-spex/claude-mdgit clone --depth 1 https://github.com/rhuss/cc-spexWrote 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/rhuss/cc-spex/claude-md)<a href="https://agentmods.dev/instructions/rhuss/cc-spex/claude-md"><img src="https://agentmods.dev/badge/instructions/rhuss/cc-spex/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 | $0.00692 | $0.00692 |
| Opus 5 | $0.00346 | $0.00346 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
cc-spex 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cc-spex Development Guidelines
Auto-generated from all feature plans. Last updated: 2026-04-22
Active Technologies
- Bash (POSIX-compatible), Markdown, Python 3 (hooks),
jq,yq,specifyCLI (spec-kit)
Project Structure
spex/
extensions/ # Extension bundles
spex/ # Core spex extension (brainstorm, ship, using-superpowers)
spex-gates/ # Quality gates (review-spec, review-code, review-plan, stamp)
spex-worktrees/ # Git worktree isolation
spex-teams/ # Parallel agent orchestration
spex-deep-review/ # Multi-agent code review
spex-collab/ # Collaborative PR workflows
spex-detach/ # Strip spec artifacts for upstream PRs
skills/ # Standalone skills (init/)
scripts/ # Shell/Python scripts and hooks
docs/ # Tutorials and help
specs/ # Feature specifications (historical)
Code Style
Bash (POSIX-compatible, uses jq for JSON), Markdown for commands/skills: Follow standard conventions
Extensions
spex: Core extension with brainstorm, ship, flow state, and methodology entry pointspex-gates: Quality gates on speckit commands (review-spec, review-code, review-plan, stamp, verification)spex-worktrees: Git worktree isolation after speckit.specify (creates sibling worktree, restores main)spex-teams: Parallel implementation via Claude Code Agent Teams (experimental)spex-deep-review: Multi-agent code review with 5 specialized review agents and autonomous fix loopspex-collab: Collaborative PR workflows (REVIEWERS.md, phase-split, phase-manager, revise, reconcile)spex-detach: Strip spec artifacts at PR time for contributing to repos that don't use SDD
GitHub Issues
NEVER create a GitHub issue (via gh issue create or any other mechanism) without first showing the full issue content (title, labels, body) to the user for review and getting explicit approval. This applies to all repos, not just this one.
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 First seen · 64 lines · 692 tokens per session scan A ff452fa0d960
cc-spex CLAUDE.md is an instructions file published in the GitHub repository rhuss/cc-spex (114 stars, last pushed 16d ago), licensed Apache-2.0. It adds 692 tokens to every session, about $0.0035 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.