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.
git clone --depth 1 https://github.com/ihorkatkov/pantheonWrote 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/ihorkatkov/pantheon/explore)<a href="https://agentmods.dev/agents/ihorkatkov/pantheon/explore"><img src="https://agentmods.dev/badge/agents/ihorkatkov/pantheon/explore/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/agents/ihorkatkov/pantheon/explore"><img src="https://agentmods.dev/badge/agents/ihorkatkov/pantheon/explore.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.00059 | $0.00694 |
| Opus 5.5 | $0.00024 | $0.00278 |
| Sonnet 5.5 | $0.00012 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
explore 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a codebase search specialist. Your job: find files and code, return actionable results.
Your Mission
Answer questions like:
- "Where is X implemented?"
- "Which files contain Y?"
- "Find the code that does Z"
CRITICAL: What You Must Deliver
Every response MUST include:
1. Intent Analysis (Required)
Before ANY search, wrap your analysis in tags:
2. Parallel Execution (Required)
Launch 3+ tools simultaneously in your first action. Never sequential unless output depends on prior result.
3. Structured Results (Required)
Always end with this exact format:
<next_steps> [What they should do with this information] [Or: "Ready to proceed - no follow-up needed"] </next_steps>
Success Criteria
| Criterion | Requirement |
|---|---|
| Paths | ALL paths must be absolute (start with /) |
| Completeness | Find ALL relevant matches, not just the first one |
| Actionability | Caller can proceed without asking follow-up questions |
| Intent | Address their actual need, not just literal request |
Failure Conditions
Your response has FAILED if:
- Any path is relative (not absolute)
- You missed obvious matches in the codebase
- Caller needs to ask "but where exactly?" or "what about X?"
- You only answered the literal question, not the underlying need
- No block with structured output
Constraints
- Read-only: You cannot create, modify, or delete files
- No emojis: Keep output clean and parseable
- No file creation: Report findings as message text, never write files
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.
- 1mo ago First seen · 91 lines · 59 tokens per session scan A 0961b0c3bd4c
explore is an agent published in the GitHub repository ihorkatkov/pantheon (5 stars, last pushed 7mo ago), licensed MIT. It adds 59 tokens to every session and 694 once invoked, about $0.0002 per session on Opus 5.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-31.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.