spectre: Skill for Claude Code

.agents/skills/verify-spectre/SKILL.md

verify-spectre is a skill for Claude Code from joenandez/spectre. It costs 132 tokens per session (1,374 once invoked), scanned A, original, MIT.

A verification tool for the Spectre plugin, which contains coding-agent skills, hooks, prompts, and related files.

In plain words
What is it for?
Run it after changing Spectre files and before releases to check structure, tests, Codex synchronization, command-line behavior, and release readiness.
Why use it?
It catches failures that may not produce errors, such as renamed skills no longer triggering or an outdated Codex copy being served.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents); mentions Codex.

This is joenandez/spectre's own configuration. It tells Claude Code how to work on spectre itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything spectre configures →

Reuse

Borrowing it

Nothing to install: this file belongs to joenandez/spectre. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/joenandez/spectre/main/.agents/skills/verify-spectre/SKILL.md
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 verify-spectre

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/joenandez/spectre/verify-spectre"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/verify-spectre.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 132 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,374 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.00132 $0.01374
Opus 5.5 $0.00053 $0.00550
Sonnet 5.5 $0.00026 $0.00275
Haiku 4.5 $0.00013 $0.00137

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

Security

Grade A, and why

verify-spectre 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 6 executable files (scripts/gate1_structure.mjs, scripts/gate3_codex.mjs, scripts/gate4_cli.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.

.agents/skills/verify-spectre/SKILL.md · 61 lines

How it starts

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

verify-spectre

The gate suite for the Spectre plugin itself. Run it after any change to skills, agents, hooks, src/lib/, or the Codex mirror — and always before a release.

The reason this exists as scripts rather than a checklist: Spectre's real failures are silent. A skill whose frontmatter name drifts from its directory never triggers. A stale Codex mirror serves every Codex user the previous version indefinitely. A missing SessionStart registry or exact-load path leaves project knowledge undiscoverable without blocking the user's work. None of these break a test or throw an error — they just quietly stop working. So every check asserts an observable condition (file contents, exit code, byte-comparison) and exits nonzero. Nothing here is eyeballed.

Run it

node .agents/skills/verify-spectre/scripts/verify.mjs            # gates 1-4 (default, pre-commit)
node .agents/skills/verify-spectre/scripts/verify.mjs --fast     # gates 1-2 (seconds, on every change)
node .agents/skills/verify-spectre/scripts/verify.mjs --release  # gates 1-5 (before publishing)
node .agents/skills/verify-spectre/scripts/verify.mjs --gate 4   # one gate, when iterating on a fix

The scripts live alongside this skill under .agents/skills/verify-spectre/scripts/ and are the single canonical copy tracked by the public repository. Keeping the executable gates beside the skill makes a fresh clone independently verifiable without relying on ignored .claude/ state.

Run from the repo root. The scripts locate the repo from their own path, so they work regardless of your working directory.

Report the PASS/FAIL summary. On failure, each check already names what was expected and what was found — quote that rather than re-deriving it.

The gates

# Gate Asserts
1 structure Skill/agent frontmatter valid and name matches its directory · expected-skills manifest intact · hooks.json parses, scripts exist, SessionStart order is bootstrap → handoff-resume → load-knowledge · no active skill contains {{REGISTRY}} · no stale fork naming · every Skill(spectre-x) / /spectre:spectre-x / @spectre:agent reference resolves · four canonical version files agree
2 tests npm test passes; reports the test count so a silent drop (deleted tests, not fixed ones) is visible
3 codex sync-codex --check is clean — the committed mirror matches canonical source · generated hooks reference .mjs, never .cjs, and every referenced script exists · user commands use $spectre:spectre-* and skill paths use .agents/skills/
4 real-cli The CLI and hooks actually run, in throwaway temp dirs with a fresh CODEX_HOME (see below)
5 release Clean tree · mirror in sync · versions in lockstep · tag free · GitHub authenticated

Read the full file on GitHub · 61 lines

Files

What ships with it

7 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 90faa5a85743
  2. 2mo ago First seen · 61 lines · 132 tokens per session scan A d966ba846026

Subscribe to this mod's changes

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

Related

verify-spectre compared with skills from other repositories

verify-spectre next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
verify-spectrejoenandez/spectreSkill1641mo agoMITA132Claude 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.jsSkill143ktodayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143ktodayMITA103Claude Code