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 skills add joenandez/spectre --skill spectre-plan_reviewgit clone --depth 1 https://github.com/joenandez/spectreWrote 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/skills/joenandez/spectre/spectre-plan_review)<a href="https://agentmods.dev/skills/joenandez/spectre/spectre-plan_review"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/spectre-plan_review/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/skills/joenandez/spectre/spectre-plan_review"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/spectre-plan_review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.01090 |
| Opus 5 | $0.00015 | $0.00545 |
| Sonnet 5 | $0.00006 | $0.00218 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
spectre-plan_review 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 yesterday.
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plan_review
Purpose
Produce the smallest correct plan through one evidence wave, correctness review, then subtraction-first simplification.
Inputs
$ARGUMENTS: feature root/name or exact selected plan path; optional explicit authority sources,--auto-apply scope-safe,--orchestrated.- Require the selected plan or route to
spectre-create_plan. Authority sources areconcepts/scope.md,specs/prd.md,specs/ux.md, explicittask_context.mdrequirements, or the selected plan's explicit requirements/boundaries when no separate Scope exists. Reuse existing research.
Working Set
- Reuse a managed
FEATURE_ROOTonly 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 followSkill(spectre-feature-root)through DONE; orchestrated calls escalate. Keep writes beneath it and pass it unchanged. - Review the exact selected plan path. Never copy its prose into another authoritative plan, overwrite a sibling plan, or manufacture a second Scope document.
- Reports:
reviews/plan_correctness.mdandreviews/plan_review.md. Resume a sole correctness report only when its post-edit hash matches the selected plan; otherwise use absent canonical paths or timestamped siblings.
Outputs + DONE
plan_correctness.md: route/model metadata and hashes; evidence/unknowns; findings; retained constraints/tests; dispositions and resulting edits.plan_review.md: correctness path/hash; deletions, collapses, reuse, deferrals, retained exceptions, test reductions, findings/dispositions, and structural Before → After.- Reports are deltas; never restate the plan.
DONE when both stages complete; research ran once at most; every mechanism traces to a current requirement, constraint, prerequisite, or verified fact; every new complexity boundary has a valid exception; the plan is smaller in mechanisms, surfaces, process, or tests—or proves no safe reduction; behavior and constraints survive; no correctness Blocker/High remains; scope changes are withheld; findings are disposed; hashes/write bounds pass; and direct-mode Verification is executable.
What ships with it
2 files 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.
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.
- yesterday Changed · +6 lines ad9ff3028c25
- 4d ago Changed · +1 lines 31abf1f3242a
- 6d ago Changed 3fd852e2cd8c
- 7d ago Changed · -3 lines · -6 tokens per session 6d443d2402e8
- 12d ago First seen · 55 lines · 35 tokens per session scan A dd908545a7f3
spectre-plan_review is a skill published in the GitHub repository joenandez/spectre (161 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 1,090 once invoked, about $0.0001 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…