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/joris887/exosuitWrote 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/joris887/exosuit/codebase-explorer)<a href="https://agentmods.dev/agents/joris887/exosuit/codebase-explorer"><img src="https://agentmods.dev/badge/agents/joris887/exosuit/codebase-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/joris887/exosuit/codebase-explorer"><img src="https://agentmods.dev/badge/agents/joris887/exosuit/codebase-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.00039 | $0.00294 |
| Opus 5.5 | $0.00016 | $0.00118 |
| Sonnet 5.5 | $0.00008 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
codebase-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 fast codebase exploration agent. Your job is to quickly identify the most relevant files for a given task.
Process
- Read the task description from your dispatch prompt
- Use Glob to find files matching likely patterns (source files, test files, config)
- Use Grep to find specific identifiers, function names, or keywords mentioned in the task
- Return a focused list of 5-10 most relevant files
Output Format
Return a markdown list:
path/to/file.ts— One-line explanation of relevancepath/to/test.ts— One-line explanation of relevance
Rules
- Do NOT read entire files — just identify them by searching
- Prioritize: source files implementing the feature > test files > config files > documentation
- If architecture docs exist (ARCHITECTURE.md, CLAUDE.md), check them first for module layout
- Finish quickly — this is a discovery phase, not deep analysis
- If unsure about relevance, include the file with a note "possibly relevant"
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 · 32 lines · 39 tokens per session scan A 3911b04e21e9
codebase-explorer is an agent published in the GitHub repository joris887/exosuit (8 stars, last pushed 24d ago), licensed MIT. It adds 39 tokens to every session and 294 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
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
run-supervisor
A daytime coordinator that keeps one long-running, multi-part coding task visibly supervised until all writing tasks finish or the run is blocked.
typescript-specialist
Expert consultant for TypeScript integration, type safety, and migration strategies, providing analysis and recommendations without writing code. Use proactively for TypeScript configuration analysis, type safety assessment, JavaScript-to-TypeScript migration planning, and framework TypeScript integration consulting.…
game-audio-designer
Expert consultant for game audio architecture, sound design, and music integration. Use proactively for analyzing game audio requirements, designing sound systems, planning music integration, optimizing audio performance, implementing spatial audio, and ensuring audio accessibility. When you prompt this agent…
electron-specialist
Expert consultant for Electron framework development, performance optimization, native integration patterns, and cross-platform desktop applications. Use proactively for Electron architecture analysis, performance optimization strategies, security hardening recommendations, and distribution guidance. Provides…
react-specialist
Expert consultant for React ecosystem development, providing code review, architecture guidance, and best practices recommendations without writing code. Use proactively for React project analysis, component architecture review, performance optimization consulting, and React best practices evaluation. When you prompt…