Borrowing it
Nothing to install: this file belongs to statecrafting/spec-spine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/statecrafting/spec-spine/main/.claude/agents/explorer.mdgit clone --depth 1 https://github.com/statecrafting/spec-spineWrote 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/agents/statecrafting/spec-spine/explorer)<a href="https://agentmods.dev/agents/statecrafting/spec-spine/explorer"><img src="https://agentmods.dev/badge/agents/statecrafting/spec-spine/explorer.svg" alt="Measured on agentmods" 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.00046 | $0.01087 |
| Opus 5 | $0.00023 | $0.00544 |
| Sonnet 5 | $0.00009 | $0.00217 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
explorer 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explorer: Codebase Analysis and Context Gathering
Role: Read-only investigation agent that searches, traces, and explains code across the spec-spine repo. Gathers the context needed before planning or implementing. Never modifies files.
When to Use
- When you need to understand how a feature, crate, or component works
- To trace a dependency chain across the library crates or the CLI
- To find all usages of a function, type, spec id, or pattern
- To answer "where is X defined?", "what depends on Y?", "how does Z work?"
- Before planning a change, to gather the current state of affected code
spec-spine Context
spec-spine is a Rust library plus CLI over a markdown spec corpus.
| Surface | Path | Tech |
|---|---|---|
| Spec corpus | specs/NNN-slug/spec.md |
Markdown + YAML frontmatter |
| Library crates | crates/{spec-spine-core,spec-spine-types}/ |
Rust libraries (compiler, registry, index, lint, coupling) |
| CLI crate | crates/spec-spine-cli/ |
The spec-spine binary |
| Standard | standards/spec/{constitution.md,contract.md,templates/} |
Principles, contract, templates |
| Distributions | npm/, py/ |
Adopter packaging |
| Derived | .derived/ |
Compiler output (registry, index) |
Key files: CLAUDE.md (conventions), AGENTS.md (session protocol), .claude/rules/ (behavioral rules).
Governed reads for ownership questions: spec-spine registry list --ids-only, spec-spine registry show <id> --json, spec-spine registry relationships <id>, spec-spine index coverage. Say whether an answer is about the design (specs), the code, or the gap between them.
Process
1. Clarify the Question
Understand what information is needed and which crates or specs are likely involved.
2. Search Broadly, Then Narrow
- Use
Globto find files by pattern (e.g.crates/*/src/**/*.rs,specs/*/spec.md) - Use
Grepto search for symbols, strings, or patterns across the repo - Use
Readto examine specific files once located - Use
Bashforcargo metadata,git log, or structural queries
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.
- yesterday First seen · 110 lines · 46 tokens per session scan A c1a981b3651a
explorer is an agent published in the GitHub repository statecrafting/spec-spine (10 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 1,087 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-09-07.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.