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-executegit 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-execute)<a href="https://agentmods.dev/skills/joenandez/spectre/spectre-execute"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/spectre-execute.svg" alt="Measured on agentmods" 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.00033 | $0.02799 |
| Opus 5 | $0.00016 | $0.01399 |
| Sonnet 5 | $0.00007 | $0.00560 |
| Haiku 4.5 | $0.00003 | $0.00280 |
Grade A, and why
spectre-execute 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 today.
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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
execute
Preserve dependency-safe parallelism, authority, gates, repairs, finalization.
Inputs
$ARGUMENTS: path;--origin plan|fix|delegate;--preflight-plan <xs|light|standard|comprehensive>; wave hints;--orchestrated; orchestrated-only--finalization-owner parent. Default owner:self. Callers provide origin; unknown staysunknownrather than inferred.--review-profile final-only, valid only with--orchestrated --finalization-owner parent; defers intermediate review and requires the orchestrating caller to invokeSkill(spectre-code_review)exactly once on the final candidate; caller owns sequencing, never semantic review.structured: execute index + resolvabletasks.json; malformed structured input escalates, never becomes a plan.plan-direct: any explicit readable plan, including paths, Plan handoff markers, legacyExecution Mode: directheaders. The explicit supplied plan wins over ambient task artifacts and enters this preparation contract.- No path: use existing same-run source evidence first, then a plan at the confirmed root, then structured-only fallback. No-path selected plans receive this preparation before dispatch. Never infer from branch/recency.
--preflight-plan <depth>remains a preparation-depth hint, not authorization, classification, or a task-graph switch; a depth hint must not create authority pause.Execution Mode: directis a legacy coordination hint. No selected readable plan needs a completeness/header ceremony.
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. - A
--origin fixapproved bug-report source adopts its containingBUG_ROOTdirectly, before feature-root resolution. - Keep the invocation checkout.
- Structured detail precedence: declared
Tasks JSON→ adjacenttasks.json→ sibling.tasks.json; else escalate. Read index whole and task detail by targeted slices. - Structured/plan-direct read
references/telemetry.md, start/resume one local event run with origin, and follow its primary/worker authority contract. The local workflow store is the sole lifecycle/progress authority; source plans/tasks stay immutable. Summaries retain origin, shape, category, elapsed time, aggregate token measurements only. Plan-direct emits workstream events. Telemetry failure degrades observation, never delivery authority. SCOPE_DOCS: manifest paths or scope/UX/research cited by the plan.- On first selected readable-plan use/resume, read
references/plan-direct.mdfor preparation state. On the first verification failure, review finding, E2E gap, or proof failure, readreferences/repair-policy.md. - Maintain compact verification ledger by HEAD, check id, changed/dependency surface, result, attribution, disposition; controls final reruns. Never persist raw output or per-wave evidence/checkpoint/report files.
What ships with it
4 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.
- today Changed · -22 tokens per session 1203a82f639f
- 3d ago Changed · +4 lines 099a1a3abd36
- 8d ago First seen · 66 lines · 55 tokens per session scan A 8a3989567e0b
spectre-execute is a skill published in the GitHub repository joenandez/spectre (158 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 2,799 once invoked, about $0.0002 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…