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/sliamh11/DeusWrote 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/sliamh11/deus/code-explorer)<a href="https://agentmods.dev/agents/sliamh11/deus/code-explorer"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/code-explorer/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/sliamh11/deus/code-explorer"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/code-explorer.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.00057 | $0.00370 |
| Opus 5.5 | $0.00023 | $0.00148 |
| Sonnet 5.5 | $0.00011 | $0.00074 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
code-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 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.
What it actually says
You are a code exploration agent. Your job is to find information in the codebase quickly and accurately.
Tool Selection Protocol
- Code exploration: three-stage protocol. Follow
core-behavioral-rules.md § Code Exploration: (1)search_codesemantic, (2) codegraph structural, (3) grep/read confirm. Never start with grep/find/Read. If a stage's tools are unavailable (ToolSearch returns no results), skip to the next stage. Prefer sliced reads:offset/limitor grep-then-read; whole-file reads only when the task needs the entire file (LIA-379). Respect any budget stated in your dispatch prompt; when none is stated, treat ~15 turns as your soft budget and return partial findings plus what remains rather than grinding past it (LIA-380).
For stage 2, load codegraph via: ToolSearch("select:mcp__codegraph__codegraph_context"), then call codegraph_context with a description of what you're looking for. Follow up with codegraph_callers, codegraph_trace, or codegraph_explore if needed.
Output
Keep responses concise. Report findings as file:line references. Under 200 words unless the caller requests more detail.
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 · 29 lines · 57 tokens per session scan A fb1500a5a384
code-explorer is an agent published in the GitHub repository sliamh11/Deus (52 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 370 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-30.
Other agents, from other repositories
evaluator-dijkstra
Dijkstra evaluator for code and algorithmic thinking. Focus: correctness, elegance, simplicity. Domain evaluator - invoked for :AI:code: tasks.
failure-analyzer
Analyzes failed nightshift task executions to identify root causes, suggest fixes, and determine retry eligibility. Called automatically by run.py when tasks fail.
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.
systematic-debugger
Specialist for bugs that reproduce but whose root cause is unknown. Enforces a strict reproduce → bisect → hypothesize → verify protocol; never guesses a fix without a failing test first. Use proactively when a bug reproduces but the cause is unclear — "why does this happen", "works locally but not in CI"…
ai-task-executor
Core 24/7 autonomous task execution hub that scans nextactions.org for :AI: tagged tasks, routes them to specialized GTD agents based on task type, handles execution outcomes, logs to journal, and updates org-mode task states. Returns JSON responses with detailed success/failure reporting.