spectre: Skill for Claude Code

.agents/skills/spectre-rewrite-skill/SKILL.md

spectre-rewrite-skill is a skill for Claude Code from joenandez/spectre. It costs 118 tokens per session (2,953 once invoked), scanned A, original, MIT.

A guide for compressing a verbose SPECTRE skill into a shorter proposal that states what the skill must do without prescribing how to do it.

In plain words
What is it for?
Use it when rewriting or compressing a SPECTRE skill, classifying its freedom level, checking its size budget, and preparing a reviewable proposal.
Why use it?
It preserves the important requirements while reducing unnecessary instructions and making the skill easier to review.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions subagents; installed under .agents/ (shared by several agents).

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/spectre-rewrite-skill/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 spectre-rewrite-skill

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/joenandez/spectre/spectre-rewrite-skill"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/spectre-rewrite-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 118 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,953 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.00118 $0.02953
Opus 5 $0.00059 $0.01477
Sonnet 5 $0.00024 $0.00591
Haiku 4.5 $0.00012 $0.00295

Measured 11d ago against content hash 347c44e45ee5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

spectre-rewrite-skill 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 11d 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.

.agents/skills/spectre-rewrite-skill/SKILL.md · 116 lines

How it starts

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

Spectre Skill-Rewrite Proposal Generator

Turn one (or a small same-tier batch of) SPECTRE skill(s) into a proposed Spectre contract-form rewrite, grounded in the spectre-light learnings. Produces a review-ready proposal — write it to docs/tasks/spectre-light/proposals/<skill>.SKILL.md (scratch), not the live plugin.

INPUT (from $ARGUMENTS)

  • Target skill(s): the spectre-* skill name(s) in $ARGUMENTS (one, or a small same-tier batch). If absent, ask which skill to rewrite.
  • Source path(s): plugins/spectre/skills/<skill>/SKILL.md.
  • Freedom tier: classify it (below) unless the user states it.
  • Size benchmark: the source wc -c, and the tier budget from distillation §5.

All doc paths below are relative to the repo root (this skill assumes cwd = the spectre repo).

ROLE

You are a Spectre skill-compression specialist. You re-express a verbose, procedural SPECTRE skill as a compact input→output contract — clear on WHAT, silent on HOW — that preserves every load-bearing safety procedure while cutting prose the model already knows. You optimize for quality-per-token, and you treat the contract, not the procedure, as the thing that preserves quality.

You output proposals for human review. When a load-bearing element cannot survive the tier budget, you flag it, never silently cut it.

GROUND YOURSELF FIRST (read, do not summarize back)

  1. resources/spectre-light/concepts/research-distillation.md — the bundled principles, freedom-tier framing (§5), DO-NOT-STRIP list (§4), contract fields (§2), and cache/progressive-disclosure rules. (The size budget is the token tripwire in scope.md §3, not the old char ranges.)
  2. resources/spectre-light/concepts/scope.md — bundled IN/OUT/ANTI-SCOPE. Anti-scope is binding: no new capability, phase-model change, or subagent-roster change.
  3. resources/spectre-light/specs/plan.md — bundled §2 contract template, Type A/B/C/D cross-ref remap, and §6 Out-of-Bounds.
  4. The source skill(s) in full.

Read the full file on GitHub · 116 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.

  1. 11d ago First seen · 116 lines · 118 tokens per session scan A 347c44e45ee5

Subscribe to this mod's changes

spectre-rewrite-skill is a skill published in the GitHub repository joenandez/spectre (161 stars, last pushed 2d ago), licensed MIT. It adds 118 tokens to every session and 2,953 once invoked, about $0.0006 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens