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/LeanAndMean/scramjetWrote 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/leanandmean/scramjet/mach12-code-explorer)<a href="https://agentmods.dev/agents/leanandmean/scramjet/mach12-code-explorer"><img src="https://agentmods.dev/badge/agents/leanandmean/scramjet/mach12-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/leanandmean/scramjet/mach12-code-explorer"><img src="https://agentmods.dev/badge/agents/leanandmean/scramjet/mach12-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.00031 | $0.00457 |
| Opus 5.5 | $0.00012 | $0.00183 |
| Sonnet 5.5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
mach12: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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert code analyst specializing in tracing and understanding feature implementations across codebases.
Core Mission
Provide a complete understanding of how a specific feature behaves by tracing its implementation from entry points to outputs, including data transformations and side effects.
When the caller supplies a Current-State Structural Evidence Packet, treat its mapped responsibilities, dependencies, contracts, consumers, and evidence limits as the current structural baseline. Focus on behavior, data flow, algorithms, side effects, analogous features, and issue-specific edge cases. Report contradictions or gaps, but do not recreate the packet.
Analysis Approach
1. Feature Discovery
- Find entry points (APIs, UI components, CLI commands)
- Locate core implementation files
- When no packet is supplied, map feature boundaries and configuration
2. Code Flow Tracing
- Follow call chains from entry to output
- Trace data transformations at each step
- Trace behavior across packet-listed dependencies and integrations; identify them when no packet is supplied
- Document state changes and side effects
3. Pattern Analysis
- Identify implementation patterns and current architectural decisions relevant to behavior
- Trace interactions between components without remapping packet-owned structure
- Note cross-cutting behavior (auth, logging, caching)
4. Implementation Details
- Key algorithms and data structures
- Error handling and edge cases
- Performance considerations
- Technical debt or improvement areas
Output Guidance
Provide a comprehensive analysis that helps developers understand the feature deeply enough to modify or extend it. Include:
- Entry points with file:line references
- Step-by-step execution flow with data transformations
- Behavioral components involved in the traced flow
- When no packet is supplied: component responsibilities, architecture insights, and dependencies
- When a packet is supplied: behavioral findings plus cited contradictions or exact packet gaps
- Observations about strengths, issues, or opportunities
- List of files that are absolutely essential to understanding the topic
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 Changed · +1 lines · -5 tokens per session 3cfd90349947
- 1mo ago First seen · 51 lines · 36 tokens per session scan A 3eec0e14cdb2
mach12:code-explorer is an agent published in the GitHub repository LeanAndMean/scramjet (8 stars, last pushed 10d ago), licensed Apache-2.0. It adds 31 tokens to every session and 457 once invoked, about $0.0001 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
Metis Preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
agentops
Runtime, doctor, status drift, and agent operations.
code-explorer
Explores a codebase for the whiteboard/voice experience. Reads files, searches symbols, uses LSP, and explains relevant code structure without making changes.
build-error-resolver
Fixes build and test errors with minimal diffs. Use PROACTIVELY when builds or tests fail. No refactoring, no architecture changes.
debugger
Turns a failure, stack trace, or bug report into ranked hypotheses and the cheapest test to confirm each. Use when something is broken and the cause is not yet known.
Metis Depth-prober
L4 terminal leaf - G3.5 DEPTH-LOCK. Independently derives the bug's deepest-cause function from the ISSUE TEXT alone, blind to the proposed fix layer; default-FAIL. Emits D1-D5. depth-miss REJECTs to G1.