spectre-feature-root

spectre-feature-root is a skill for Claude Code from joenandez/spectre. It costs 46 tokens per session (467 once invoked), scanned A, original, MIT.

An internal setup routine that creates a standard workspace for a new Spectre feature or bug when no managed workspace exists.

In plain words
What is it for?
Use it only as part of a standalone workflow that needs a new feature or bug root. It is not for existing workspaces or direct user requests.
Why use it?
It gives later workflow steps one safe, consistent place for their files without selecting or altering an existing workspace.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Good fit Use it only as part of a standalone workflow that needs a new feature or bug root. It is not for existing workspaces or direct user requests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/joenandez/spectre/spectre-feature-root
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-feature-root
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-feature-root

README.md
[![agentmods](https://agentmods.dev/badge/skills/joenandez/spectre/spectre-feature-root/github.svg)](https://agentmods.dev/skills/joenandez/spectre/spectre-feature-root)
Your own site
<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.

agentmods 80×15 button for spectre-feature-root

Your own site · 80×15
<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>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 467 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.00046 $0.00467
Opus 5 $0.00023 $0.00234
Sonnet 5 $0.00009 $0.00093
Haiku 4.5 $0.00005 $0.00047

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

Security

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.

plugins/spectre-codex/skills/spectre-feature-root/SKILL.md · 40 lines

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

  1. Use an explicit caller candidate/descendant. Reject absolute, traversal, symlink-escaping, or unmanaged paths.
  2. Otherwise derive a concise kebab name and choose the first free .spectre/{features|bugs}/<name>[-N]/ per KIND. Never inspect or offer existing roots, ask whether to reuse one, present naming options, or wait for approval; suffixes resolve collisions.
  3. Create feature.json containing only schema_version, created_at, feature, and repo-relative feature_root; no lifecycle, alias, branch, or absolute path.
  4. Unless .spectre/ is ignored, preserve .spectre/.gitignore; require literal manifest.json, bin/, handoffs/, !features/, !bugs/, plus evidence/, checkpoints/, runs/, markers/, working_set.json, cleanup_summary.md, execution_state.md, reviews/task_review_attempt.json, reviews/task_review_safety.json under both features/**/ and bugs/**/. Specs/research/decisions/reviews/proof stay trackable. Never edit root .gitignore; warn on local-only matches.
  5. 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.

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. 6d ago Changed fed646736c86
  2. 10d ago First seen · 40 lines · 46 tokens per session scan A a4f6fd0522b1

Subscribe to this mod's changes

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.

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