spectre

spectre is a skill for Claude Code from Kasempiternal/Claude-Agent-System. It costs 32 tokens per session (5,110 once invoked), scanned B, original, MIT.

A research workflow that splits web, codebase, and document investigations among parallel agents, then combines and independently checks their findings.

In plain words
What is it for?
Use it for broad technical research, comparing information from several sources, and producing a checked report.
Why use it?
It reduces the need to research every angle yourself and helps catch unsupported claims or mistakes. It requires Agent Teams and GPT Architect to be turned off.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; names the AskUserQuestion tool.

Part of the cas plugin — 19 skills, 3 hooks, 2 MCP servers shipped together

Good fit Use it for broad technical research, comparing information from several sources, and producing a checked report.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kasempiternal/claude-agent-system/spectre
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 Kasempiternal/Claude-Agent-System --skill spectre
Clone the repo
git clone --depth 1 https://github.com/Kasempiternal/Claude-Agent-System

Made for: Claude Code.

Or install cas, the plugin that ships this one along with the rest of its 19 skills, 3 hooks, 2 MCP servers.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/kasempiternal/claude-agent-system/spectre"><img src="https://agentmods.dev/badge/skills/kasempiternal/claude-agent-system/spectre.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,110 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.00032 $0.05110
Opus 5 $0.00016 $0.02555
Sonnet 5 $0.00006 $0.01022
Haiku 4.5 $0.00003 $0.00511

Measured 8d ago against content hash 30e4f148db95, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade B, and why

spectre scanned grade B with 1 finding 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 8d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

Read `~/.claude/settings.json`. Verify `env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` is `"1"`.
claude-agent-system-plugin/skills/spectre/SKILL.md · 456 lines

How it starts

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

███████╗██████╗ ███████╗ ██████╗████████╗██████╗ ███████╗
██╔════╝██╔══██╗██╔════╝██╔════╝╚══██╔══╝██╔══██╗██╔════╝
███████╗██████╔╝█████╗  ██║        ██║   ██████╔╝█████╗
╚════██║██╔═══╝ ██╔══╝  ██║        ██║   ██╔══██╗██╔══╝
███████║██║     ███████╗╚██████╗   ██║   ██║  ██║███████╗
╚══════╝╚═╝     ╚══════╝ ╚═════╝   ╚═╝   ╚═╝  ╚═╝╚══════╝

         ⚔ Reconnaissance Swarm ⚔
          CLAUDE AGENT SYSTEM

MANDATORY: Output the banner above verbatim as your very first message to the user, before any tool calls or other output.

You are entering SPECTRE INTELLIGENCE MODE. You are Opus, the intelligence commander. You deploy parallel research agents to investigate any topic from multiple angles — synthesizing, cross-validating, and producing a structured intelligence report.

This is the SPECTRE EDITION: Research topics are decomposed into facets, parallel researchers explore each facet via web and codebase, an intelligence analyst synthesizes findings, validators cross-reference claims independently, and a compiler produces the final report.

Your Role: Intelligence Commander

  • You are the COMMANDER, not the RESEARCHER — delegate everything via Task tool with team_name
  • Create a team, spawn teammates for actual research
  • Use the shared task list (TaskCreate/TaskUpdate/TaskList) to track all phases
  • Use SendMessage to coordinate teammates and relay context between waves
  • Maximize parallelization within each wave
  • NEVER do research directly — your researchers have the tools

Phase 0: Prerequisites Check

Step 0: Enforce Delegation Mode Exclusivity

Inspect the current conversation for the latest explicit /gpt-architect on or /gpt-architect off command. New sessions default to OFF.

  • If the latest command is /gpt-architect on: STOP before calling Agent, TeamCreate, or any workflow router. Tell the user:
    SPECTRE needs Claude Agent Teams, but GPT Architect currently reserves all delegation for Codex.
    Run /gpt-architect off, then invoke /spectre again.
    
  • If OFF or never enabled: continue.

Read the full file on GitHub · 456 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. 8d ago First seen · 456 lines · 32 tokens per session scan B 30e4f148db95

Subscribe to this mod's changes

spectre is a skill published in the GitHub repository Kasempiternal/Claude-Agent-System (15 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 5,110 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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

audit

Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.

oliver-kriska/claude-elixir-phoenix · 35 tokens

review

Review code with parallel agents — tests, security, Ecto, LiveView, Oban. Use after implementation to catch bugs and anti-patterns before committing.

oliver-kriska/claude-elixir-phoenix · 34 tokens

pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 59 tokens

phx-pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 61 tokens

boundaries

Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.

oliver-kriska/claude-elixir-phoenix · 33 tokens

challenge

Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.

oliver-kriska/claude-elixir-phoenix · 34 tokens