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 Kasempiternal/Claude-Agent-System --skill spectregit clone --depth 1 https://github.com/Kasempiternal/Claude-Agent-SystemWrote 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/kasempiternal/claude-agent-system/spectre)<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.
<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>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.00032 | $0.05110 |
| Opus 5 | $0.00016 | $0.02555 |
| Sonnet 5 | $0.00006 | $0.01022 |
| Haiku 4.5 | $0.00003 | $0.00511 |
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"`. 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 callingAgent,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.
What ships with it
9 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.
- templates/analyst-prompt.md 6.0 KB
- templates/codebase-researcher-prompt.md 5.2 KB
- templates/dashboard.html 12 KB
- templates/facet-decomposition-prompt.md 3.1 KB
- templates/findings-template.md 1.6 KB
- templates/report-compiler-prompt.md 3.7 KB
- templates/report-template.md 3.4 KB
- templates/researcher-prompt.md 5.5 KB
- templates/validator-prompt.md 6.3 KB
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.
- 8d ago First seen · 456 lines · 32 tokens per session scan B 30e4f148db95
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.
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.
review
Review code with parallel agents — tests, security, Ecto, LiveView, Oban. Use after implementation to catch bugs and anti-patterns before committing.
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.
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.
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.
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.