spectre: Instructions file for Claude Code

CLAUDE.md

spectre CLAUDE.md is an instructions file for Claude Code from joenandez/spectre. It costs 1,581 tokens per session, scanned A, original, MIT.

A repository guide for spectre, a plugin that organizes coding work into stages such as defining scope, planning, executing, and cleaning up. It also describes the repository layout and release checks.

In plain words
What is it for?
Use it when changing spectre prompts, subagents, hooks, skills, synchronization scripts, or tests.
Why use it?
It explains which files are the source of truth and helps agents follow the intended workflow without editing generated files by hand.

Instructions file for Claude Code

Written for Claude Code: SessionStart hook event. Also seen: reads .claude/ paths; mentions .claude-plugin; mentions CLAUDE.md.

This is joenandez/spectre's own configuration. It tells Claude Code how to work on spectre itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything spectre configures →

Reuse

Borrowing it

Nothing to install: this file belongs to joenandez/spectre. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/joenandez/spectre/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/joenandez/spectre

Made for: Claude Code.

Wrote 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.

agentmods badge for spectre CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/joenandez/spectre/claude-md/github.svg)](https://agentmods.dev/instructions/joenandez/spectre/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/joenandez/spectre/claude-md"><img src="https://agentmods.dev/badge/instructions/joenandez/spectre/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.

agentmods 80×15 button for spectre CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/joenandez/spectre/claude-md"><img src="https://agentmods.dev/badge/instructions/joenandez/spectre/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,581 This file is loaded in full into every session.
When invoked 1,581 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01581 $0.01581
Opus 5.5 $0.00632 $0.00632
Sonnet 5.5 $0.00316 $0.00316
Haiku 4.5 $0.00158 $0.00158

Measured 1mo ago against content hash 1d4845aa4389, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spectre 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.

CLAUDE.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code when working with this repository.

Project Overview

spectre is a Claude Code and Codex plugin providing standalone Scope, then Plan, Execute, and Ship, alongside ten retained public utilities. Scope owns feature boundaries; Plan owns implementation planning; Execute owns implementation, review, and proof; Ship owns cleanup, testing, rebase, and pull request closeout. It's a meta-prompt orchestration system where prompts invoke subagents.

Repository Structure

spectre/
├── .claude-plugin/
│   └── marketplace.json  # Marketplace registration
├── plugins/
│   ├── spectre/           # Canonical plugin source
│   │   ├── .claude-plugin/
│   │   │   └── plugin.json   # Plugin manifest
│   │   ├── agents/           # Canonical subagent definitions
│   │   ├── hooks/            # Canonical learning/runtime helpers
│   │   └── skills/           # Canonical workflow and knowledge skills
│   └── spectre-codex/     # Generated Codex bundle; do not hand-edit
├── scripts/              # Release & utility scripts
├── AGENTS.md             # Codex-facing repo guidance
└── CLAUDE.md

Commands

npm test
npm run sync-codex -- --check --quiet

CLI for Other Agents: See spectre-labs/cli

Architecture

Meta-Prompt Orchestration

Skills are contract-form workflow prompts that:

  1. Parse user arguments
  2. Spawn parallel subagents (@spectre:dev, @spectre:analyst, etc.)
  3. Subagents execute specialized prompts
  4. Main prompt synthesizes findings and produces artifacts

Subagents

Agent Purpose
@spectre:dev Implementation with MVP focus
@spectre:analyst Understand how code works
@spectre:finder Find where code lives
@spectre:patterns Find reusable patterns
@spectre:web-research Web research
@spectre:tester Test automation
@spectre:reviewer Independent review

Read the full file on GitHub · 180 lines

Changes

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.

  1. 1mo ago Changed · +17 tokens per session 1d4845aa4389
  2. 1mo ago Changed · +48 tokens per session 44674f7d1982
  3. 2mo ago First seen · 180 lines · 1,516 tokens per session scan A 693f4faa4088

Subscribe to this mod's changes

spectre CLAUDE.md is an instructions file published in the GitHub repository joenandez/spectre (164 stars, last pushed 1mo ago), licensed MIT. It adds 1,581 tokens to every session, about $0.0063 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-30.

Related

spectre CLAUDE.md compared with instructions from other repositories

spectre CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
spectre CLAUDE.mdjoenandez/spectreInstructions file1641mo agoMITA1,581Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode