What is spectre-fix-core?

An internal repair workflow for a Spectre bug-fixing process. It investigates a failure, traces its cause and affected behavior, and supports a verified repair using a failing test followed by a passing implementation.

Use it only through the specified Spectre parent workflows to diagnose a bug, trace its impact, implement an approved repair, and verify the result.

It helps connect an error to its actual cause and prevents a fix from being made without reproducing and verifying the behavior.

spectre-fix-core — 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-fix-core

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-fix-core/github.svg)](https://agentmods.dev/skills/joenandez/spectre/spectre-fix-core)

Your own site

<a href="https://agentmods.dev/skills/joenandez/spectre/spectre-fix-core"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/spectre-fix-core/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-fix-core"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/spectre-fix-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 652 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.00045	$0.00652
Opus 5.5	$0.00018	$0.00261
Sonnet 5.5	$0.00009	$0.00130
Haiku 4.5	$0.00005	$0.00065

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

Security

Grade A, and why

spectre-fix-core 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.

plugins/spectre-codex/skills/spectre-fix-core/SKILL.md · 46 lines

How it starts

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

fix-core

Purpose

Own the diagnostic phase of the bug flow: reproduce the failure, ground the root cause and behavioral blast radius, then return a source-faithful Execute handoff. Execute owns all code changes.

Inputs

Bug report: error, stack trace, reproduction, and referenced context.
PHASE=diagnose.
--orchestrated — withhold user-facing routing, never content.

Working Set

Read affected paths and recent changes just-in-time.
Invoking this workflow IS the user's request for subagent investigation: dispatch @spectre_analyst for causal and impact traces. Keep returns compact and in-thread, with no scratch reports.

Outputs + DONE

diagnose → DIAGNOSIS_READY: reproduction, root cause, affected files, candidate repair, evidence-backed experience contract, and regression/invariant opportunities; no code writes.

DONE when: root cause is grounded and its hypotheses were traced by dispatched analysts; the product and technical direct blast radius was independently explored after the candidate repair boundary was known; no row is unresolved; and the parent receives the diagnosis result.

Method / guardrails

Diagnose. Generate 5–7 hypotheses; reduce to 1–2 via evidence/data-flow/changes/paths; dispatch parallel @spectre_analyst traces; reproduce; synthesize one cause-level repair.
Explore product + technical impact. Once root cause and candidate repair boundary are grounded, dispatch ≥1 independent read-only @spectre_analyst; parallelize separable product journeys or technical boundaries. Trace shared callers, state, and data paths through to user/operator-observable outcomes. Return compact experience-contract rows that explicitly identify experiences that change, remain invariant, or are unresolved; synthesize and deduplicate the results.
Honor phase. diagnose returns DIAGNOSIS_READY before any code write.
Contain scope. Do not propose behavior beyond the reported repair boundary. An unresolved row or a new experience-contract row returns to the user for clarification.

Read the full file on GitHub · 46 lines

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 · -9 lines · -2 tokens per session 6639104f2bb8
1mo ago Changed 43217fb646f8
2mo ago Changed · -2 lines 1f54b6680693
2mo ago First seen · 57 lines · 47 tokens per session scan A bc4b17ef53ee

Subscribe to this mod's changes

spectre-fix-core is a skill published in the GitHub repository joenandez/spectre (164 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 652 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.

Debugging

spectre-fix-core next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
spectre-fix-corejoenandez/spectre	Skill	164	1mo ago	MIT	A	45	Claude Code
systematic-debuggingopen-metadata/OpenMetadata	Skill	16k	yesterday	Apache-2.0	A	37	Claude Code
log-error-digestzebbern/claude-code-guide	Skill	4.7k	3d ago	MIT	A	71	Claude Code, Codex
cwv-optimizeradobe/skills	Skill	319	yesterday	Apache-2.0	A	112	Claude Code
ci-fixersipyourdrink-ltd/bernstein	Skill	1.2k	yesterday	Apache-2.0	A	15	Claude Code, Codex
incident-response-incident-responsermyndharis/antigravity-skills	Skill	1.9k	23d ago	MIT	A	36	Claude Code
triaging-web-analytics-supportPostHog/posthog	Skill	41k	yesterday	none	A	151	Claude Code, Codex