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-fix-coregit 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-fix-core)<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.
<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>- 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.00047 | $0.01069 |
| Opus 5 | $0.00023 | $0.00535 |
| Sonnet 5 | $0.00009 | $0.00214 |
| Haiku 4.5 | $0.00005 | $0.00107 |
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 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fix-core
Purpose
Own one reusable bug flow: reproduce the failure, ground the root cause and behavioral blast radius, then implement a verified RED-before-GREEN repair. Standalone Fix owns the Execute handoff; orchestrated parents supply scope-bound authorization.
Inputs
- Bug report: error, stack trace, reproduction, and referenced context.
PHASE=diagnose | full.fullrequiresPARENT=spectre-delegate,PARENT_AUTHORIZATION={scope.md},AUTHORIZED_SCOPE_SHA256, andALIGNMENT_MODE=inferred.--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_analystfor causal and impact traces. Keep returns compact and in-thread, with no scratch reports. - In parent-authorized
full, read the scope artifact before any code write.
Outputs + DONE
Experience-contract rows map technical evidence to product behavior: journey/surface | current experience | expected experience | technical path/consumer | disposition=intended-change|preserved-invariant|collateral-change|unresolved | evidence | verification.
diagnose→DIAGNOSIS_READY: reproduction, root cause, affected files, candidate repair, evidence-backed experience contract, and regression/invariant opportunities; no code writes.full→FIX_COMPLETE: diagnosis, row-level contract evidence, confirmed RED, implementation, GREEN checks,[🪳 TEMP {TOPIC}]diagnostic logging, changed files, and limitations.
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; for full, authorization is valid, the intended regression is RED→GREEN, affected checks have no attributable failure, and unrelated findings are routed; and the parent receives the result.
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 43217fb646f8
- 6d ago Changed · -2 lines 1f54b6680693
- 11d ago First seen · 57 lines · 47 tokens per session scan A bc4b17ef53ee
spectre-fix-core is a skill published in the GitHub repository joenandez/spectre (161 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,069 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.