What is spectre-scope?

A workflow for defining what a new feature or improvement includes, excludes, and must explicitly avoid before technical planning or coding.

Use it to investigate a feature in the repository, resolve important questions, and write a scope document covering IN, OUT, and ANTI-SCOPE areas.

It turns an unclear request into agreed boundaries, user value, assumptions, and decisions, reducing accidental expansion of the work.

spectre-scope — Skill for Claude Code by joenandez/spectre

Install

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.

Any agent

npx skills add joenandez/spectre --skill spectre-scope

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/joenandez/spectre/spectre-scope/github.svg)](https://agentmods.dev/skills/joenandez/spectre/spectre-scope)

Your own site

<a href="https://agentmods.dev/skills/joenandez/spectre/spectre-scope"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/spectre-scope/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/joenandez/spectre/spectre-scope"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/spectre-scope.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,404 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00076	$0.01404
Opus 5.5	$0.00030	$0.00562
Sonnet 5.5	$0.00015	$0.00281
Haiku 4.5	$0.00008	$0.00140

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

Security

Grade A, and why

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

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/ensure-codex-agents.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/spectre-codex/skills/spectre-scope/SKILL.md · 70 lines

How it starts

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

scope

Turn an unstructured request into clear scope boundaries (IN / OUT / ANTI-SCOPE), user value, load-bearing assumptions, and decisions — clear on WHAT, silent on HOW. Boundaries and user value first; defer all technical/implementation questions to $spectre:spectre-plan.

Inputs

$ARGUMENTS — the feature/problem brain-dump. If empty → greet, ask for context, and WAIT for the user.
Existing root/artifact: context for new work; reuse only for the same scope run, FROM_KICKOFF=true, or explicit resume/re-scope. On re-scope, read concepts/scope.md fully, surface settled decisions and the delta, and confirm before rewriting the immutable downstream anchor.
FROM_KICKOFF=true + KICKOFF_DOC → read the doc, extract (Core Problem, User Value, Decisions Made, Remaining Ambiguities, Key Code Refs), then skip grounding + exploration and go straight to clarifications. Already-grounded.

Working Set (late-bound — read at run-time, never inline)

FEATURE_ROOT = .spectre/features/<feature-name>/, resolved from the input or proposed below.
captured session or current thread memory for this area, if present
Reuse current-request knowledge results/loads; otherwise follow Project knowledge routing. Search actual task across mixed knowledge/work previews; assess, then exact-load applicable records. Standalone #tag: exact search --tag, assess previews, then exact-load applicable matches; never guessed loads. Refine only for an unresolved question or new subject. Keep IDs/revisions in concepts/scope.md; previews/unloaded candidates are not evidence.

Feature root contract

Reuse a managed FEATURE_ROOT only when explicit/current-thread evidence ties it to this work (physical directory wins; never branch/recency/lifecycle/scans); distinct work ignores ambient roots. Otherwise, including on collision, standalone MUST first load and follow Skill(spectre-feature-root) through DONE; orchestrated calls escalate. Keep writes beneath it and pass it unchanged.

Read the full file on GitHub · 70 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

scripts/ensure-codex-agents.mjs 12 KB runs code

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.

1mo ago Changed · +2 lines 6d7a47146bdc
1mo ago Changed 6502ea9dd544
2mo ago Changed · -1 lines 705b09908229
2mo ago First seen · 69 lines · 76 tokens per session scan A e4b7d5a99656

Subscribe to this mod's changes

spectre-scope is a skill published in the GitHub repository joenandez/spectre (164 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 1,404 once invoked, about $0.0003 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.

Planning

spectre-scope next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
spectre-scopejoenandez/spectre	Skill	164	1mo ago	MIT	A	76	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code