agentmods.dev

spectre-execute

spectre-execute is a skill for Claude Code from joenandez/spectre. It costs 33 tokens per session (3,358 once invoked), scanned A, original, MIT.

A task runner that follows a written plan in dependency-safe groups, checking affected work and reviewing the result before finishing.

In plain words
What is it for?
Use it to execute a feature or other artifact plan, resume planned work, verify affected parts, and perform final review. It does not create plans or handle unplanned fixes.
Why use it?
It helps carry out planned work in the right order and catches problems without putting every implementation detail into the main working context.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions Codex.

not rated 164repo +1 changed 1mo ago A scan SkillSpector: pass 33 tokens original MIT

Good fit Use it to execute a feature or other artifact plan, resume planned work, verify affected parts, and perform final review. It does not create plans or handle unplanned fixes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/joenandez/spectre/spectre-execute
View source ↗ 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-execute
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-execute

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/joenandez/spectre/spectre-execute"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/spectre-execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,358 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.03358
Opus 5.5 $0.00013 $0.01343
Sonnet 5.5 $0.00007 $0.00672
Haiku 4.5 $0.00003 $0.00336

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

Security

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 1mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (references/proof/scripts/validate-proof-html.mjs, references/scripts/task-review-safety.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-execute/SKILL.md · 82 lines

How it starts

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

execute

Preserve parallelism, authority, gates, repair.

Inputs

  • $ARGUMENTS: path; --origin plan|fix; --preflight-plan <xs|light|standard|comprehensive>; wave hints; --orchestrated; orchestrated-only --finalization-owner parent. Default owner: self.
  • --review-profile final-only, valid only with --orchestrated --finalization-owner parent; it defers intermediate review and requires the orchestrating caller to invoke Skill(spectre-code_review) exactly once; caller owns sequencing, never semantic review.
  • structured: execute index + resolvable tasks.json; malformed structured input escalates, never becomes a plan.
  • fix-source: bug-report path/root or identifying content—not --origin—selects fix; load references/fix-source.md, not Plan preparation.
  • plan-direct: explicit readable plan, including paths, Plan handoff markers, and legacy Execution Mode: direct headers. 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 task-graph switch; a depth hint must not create authority pause. Execution Mode: direct is a legacy coordination hint. No selected readable plan needs a completeness/header ceremony.

Working Set

  • 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.
  • Keep the invocation checkout.
  • Structured detail precedence: declared Tasks JSON → adjacent tasks.json → sibling .tasks.json; else escalate. Read whole; detail targeted slices.
  • Structured/plan-direct read references/telemetry.md, start/resume local event run with origin, follow primary/worker authority. Local workflow store is the sole lifecycle/progress authority; plans/tasks immutable. Summaries retain origin/shape/category/elapsed/aggregate tokens; Plan-direct emits 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.md for preparation state. On the first verification failure, review finding, E2E gap, or proof failure, read references/repair-policy.md.
  • Maintain compact verification ledger by HEAD, check id, changed/dependency surface, result, attribution, disposition; controls reruns. Never persist raw output or per-wave evidence/checkpoint/report files.

Read the full file on GitHub · 82 lines

Files

What ships with it

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

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 cac73a0f638f
  2. 1mo ago Changed 8209237433d5
  3. 1mo ago Changed 7de1a5c234d2
  4. 1mo ago Changed bd8d7f148a8b
  5. 1mo ago Changed · +1 lines b34709e3ab3a
  6. 1mo ago Changed · +11 lines 101b5349fad6
  7. 2mo ago Changed · -22 tokens per session 1203a82f639f
  8. 2mo ago Changed · +4 lines 099a1a3abd36
  9. 2mo ago First seen · 66 lines · 55 tokens per session scan A 8a3989567e0b

Subscribe to this mod's changes

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

spectre-execute compared with skills from other repositories

spectre-execute next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
spectre-executejoenandez/spectreSkill1641mo agoMITA33Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code