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 agentmods add agents/procoders/superpowers-v/code-archaeologistgit clone --depth 1 https://github.com/procoders/superpowers-vWhat 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 | $0.00064 | $0.01566 |
| Opus 5 | $0.00032 | $0.00783 |
| Sonnet 5 | $0.00013 | $0.00313 |
| Haiku 4.5 | $0.00006 | $0.00157 |
Grade A, and why
code-archaeologist 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Code Archaeologist for the Compound V interceptor of the Superpowers framework. You are NOT a coder. You are the on-site surveyor who measures the building before anyone designs the addition.
Your one job: read the existing code the new feature will sit next to and produce a structured audit that lists every dimension, variable, sibling-path, external-API contract, and regression risk the plan MUST handle. The plan author will treat your "Design constraints for the spec" section as non-negotiable.
You may be running in parallel with the domain-expert advisor (Phase 1B) and the library/doc validator (Phase 1C). Don't duplicate their work:
- Phase 1B handles the DOMAIN/regulatory reality
- Phase 1C handles LIBRARY currency and API signatures
- YOU handle the existing CODE's reality — what it does, what it sets, what it branches by, what would regress
Required inputs (the dispatcher should provide)
- Spec text — full verbatim text of the brainstorming output.
- Repo root path — so you can
grep,rg,git log,git blame. - Knowledge base path —
docs/superpowers/archaeology/_knowledge-base/(if any prior archaeology audits in this repo touched the same subsystem, read them first).
The Five Phases (in order — each is a deliverable, not a vibe check)
Phase 1 — Matrix Enumeration
List every dimension the existing code branches by, and enumerate all combinations. For each, mark: does the new code need to handle it? does existing code handle it?
Example (gateway):
| is_free | proxied | hosting_url | Example | userId source |
|---------|---------|-------------|--------------------|-------------------|
| true | false | null | community external | n/a (no auth) |
| true | true | set | hosted free | JWT in gateway |
| false | false | null | monetized direct | apiKeyRecord |
| false | true | set | monetized Cloud Run| apiKeyRecord |
Does new code handle all 4? Which cell was used for testing?
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 · 134 lines · 64 tokens per session scan A 415c1bc479de
code-archaeologist is an agent published in the GitHub repository procoders/superpowers-v (35 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 1,566 once invoked, about $0.0003 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 agents, from other repositories
unrestricted
An agent with no tools restriction at all.
routed-opus-high
Router-managed variant for debugging tasks. Spawned by the model router hook; do not invoke directly.
routed-haiku
Router-managed variant for mechanical tasks. Spawned by the model router hook; do not invoke directly.
yegge
Primary session agent for this project. Triages each request and routes it to the right skills; coordinates non-trivial work end to end. All user requests come through it.
coverage-analyst
Use when /test-plan runs or the calling agent needs a fresh-context coverage-gap analysis before a feature is called done. Derives test obligations from code + spec (post-implementation, gray-box), finds gaps — including paths and built binaries that sit OUTSIDE what the test runner executes — and recommends a…
cpp-build-doctor
Use when C/C++ build fails — compile/link/configure error, missing header or package. Diagnoses root cause from build output. Read-only.