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-plangit 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)<a href="https://agentmods.dev/skills/joenandez/spectre/spectre-plan"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/spectre-plan/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"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/spectre-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 34 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00049 | $0.01458 |
| Opus 5.5 | $0.00020 | $0.00583 |
| Sonnet 5.5 | $0.00010 | $0.00292 |
| Haiku 4.5 | $0.00005 | $0.00146 |
Grade A, and why
spectre-plan 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.
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
Purpose
Turn confirmed Scope into the smallest draft and handoff. spectre-plan-route classifies; primary owns plan. Scope remains immutable.
Inputs
$ARGUMENTS: confirmed Scope—thread or managed root/descendant. Repository changes without Scope return tospectre-scope; bugs usespectre-fix. Read-only diagnosis/review, release, and approved-artifact execution remain direct.- Existing Scope/PRD,
ux.md(preferred) or legacyspecs/ux.md,task_context.md, and prior plans.
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. - Immutable canonical Scope:
concepts/scope.mdwhen present, else confirmed thread; never change it without explicit scope-change approval. - Read
references/estimation-guidance.mdwhen applicable; each estimate excludes waits and never delays or blocks the gate. - 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 intask_context.md; previews/unloaded candidates are not evidence.
Outputs + DONE
Every route writes specs/plan.md and task_context.md with Scope/authority-bound ## Minimum Solution Selection; no review/task/index/task-review artifacts.
DONE when task_context.md binds initial/observed routing to draft/authority hashes; Scope is unchanged; plan.completed records draft; handoff gives alignment/Trade-offs; telemetry is complete|degraded, or authority/scope stops it.
What ships with it
5 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.
- 1mo ago Changed f1cb724d6524
- 1mo ago Changed bfe4a7ce0c62
- 1mo ago Changed · +2 lines 427b1a0d1920
- 1mo ago Changed · +3 lines 5f9be448200d
- 1mo ago Changed · +6 lines 8f490bdbfb35
- 2mo ago Changed f7f76b9bde10
- 2mo ago Changed · -13 lines · -3 tokens per session d3610f7ad539
- 2mo ago Changed 4b2d4833ec64
- 2mo ago First seen · 61 lines · 52 tokens per session scan A 9f657c5a9e51
spectre-plan is a skill published in the GitHub repository joenandez/spectre (164 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,458 once invoked, about $0.0002 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.
spectre-plan compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| spectre-planjoenandez/spectre | Skill | 164 | 1mo ago | MIT | A | 49 | Claude Code, Codex |
| 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 |