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-feature-rootgit 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-feature-root)<a href="https://agentmods.dev/skills/joenandez/spectre/spectre-feature-root"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/spectre-feature-root/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-feature-root"><img src="https://agentmods.dev/badge/skills/joenandez/spectre/spectre-feature-root.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.00046 | $0.00467 |
| Opus 5 | $0.00023 | $0.00234 |
| Sonnet 5 | $0.00009 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
spectre-feature-root 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 6d 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.
What it actually says
feature-root
Purpose
Create a canonical root with no naming/reuse gate.
Inputs
Work/name hint; KIND=feature|bug (default feature); repo-relative candidate; write authority.
Working Set
Read exact candidates/ignore state only; never select existing work.
Outputs + DONE
Return FEATURE, repo-relative FEATURE_ROOT, warnings. DONE: valid root, neutral marker, tenancy, no phase artifact.
Method / guardrails
- Use an explicit caller candidate/descendant. Reject absolute, traversal, symlink-escaping, or unmanaged paths.
- Otherwise derive a concise kebab name and choose the first free
.spectre/{features|bugs}/<name>[-N]/perKIND. Never inspect or offer existing roots, ask whether to reuse one, present naming options, or wait for approval; suffixes resolve collisions. - Create
feature.jsoncontaining onlyschema_version,created_at,feature, and repo-relativefeature_root; no lifecycle, alias, branch, or absolute path. - Unless
.spectre/is ignored, preserve.spectre/.gitignore; require literalmanifest.json,bin/,handoffs/,!features/,!bugs/, plusevidence/,checkpoints/,runs/,markers/,working_set.json,cleanup_summary.md,execution_state.md,reviews/task_review_attempt.json,reviews/task_review_safety.jsonunder bothfeatures/**/andbugs/**/. Specs/research/decisions/reviews/proof stay trackable. Never edit root.gitignore; warn on local-only matches. - Write only root initialization.
Handoff
Return values/warnings; caller owns routing.
Escalate-If
Unsafe candidate/escape, marker/root conflict, or insufficient write authority. Naming ambiguity or collision never escalates.
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.
- 6d ago Changed fed646736c86
- 10d ago First seen · 40 lines · 46 tokens per session scan A a4f6fd0522b1
spectre-feature-root is a skill published in the GitHub repository joenandez/spectre (161 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 467 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…