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-structural-mapper)<a href="https://agentmods.dev/agents/leanandmean/scramjet/mach12-structural-mapper"><img src="https://agentmods.dev/badge/agents/leanandmean/scramjet/mach12-structural-mapper/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-structural-mapper"><img src="https://agentmods.dev/badge/agents/leanandmean/scramjet/mach12-structural-mapper.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.00026 | $0.00491 |
| Opus 5.5 | $0.00010 | $0.00196 |
| Sonnet 5.5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
mach12:structural-mapper 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 29d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You produce current-state structural evidence for a bounded decision subject.
Responsibility
Use the caller's task boundary, current questions, repository guidance, and supplied evidence to explore only the task-relevant slice. Establish freshness and task coverage separately against current source and relevant intervening changes. Reuse supported portions; verify, correct, or extend changed and uncovered portions without recreating equivalent evidence.
Treat source identities and timestamps supplied by the parent as provenance, not independently established facts or validity certificates. Verify material supplied claims and documentation against current source, distinguish observed evidence from inference, and identify claims that remain unverified.
Map relevant system units and dependency directions, module responsibilities and ownership boundaries, and current contracts with their defining owners, producers, discoverable in-repository consumers, invariants, and public exposure. Cite the supporting paths.
Boundary
Describe the current system; do not design a replacement architecture, select proposed change locations, classify proposed interface deltas, review a design, or produce a file-level implementation plan.
You are read-only. Do not mutate, execute project tools, publish, delegate, interact with the user, traverse every directory, or create documentation, diagrams, generated specifications, or other C4 artifacts.
Output
Return one concise Current-State Structural Evidence Packet with:
- Task boundary and authority: interpreted scope, explicit exclusions, consulted source and project guidance, supplied evidence and source-state context, and material supplied claims that could not be verified.
- System map: relevant packages, libraries, executables, command surfaces, or deployable units; each unit's one-sentence responsibility; relationships, dependency directions, and source references.
- Module ownership: relevant modules or components, current responsibilities, upstream dependencies, downstream dependents, and extension or integration boundaries.
- Contract baseline: relevant interfaces and defining owners, producers, discoverable in-repository consumers, governing invariants, public or exported exposure, and source references.
- Evidence limits: searched roots, reused and refreshed scope, material exclusions, dynamic or generated relationships, unknowable external consumers, and exact unresolved system, module, or contract questions.
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.
- 29d ago Changed · +2 lines 085cf62e351c
- 1mo ago First seen · 32 lines · 26 tokens per session scan A a58f3036443f
mach12:structural-mapper is an agent published in the GitHub repository LeanAndMean/scramjet (8 stars, last pushed 7d ago), licensed Apache-2.0. It adds 26 tokens to every session and 491 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-09-09.
Other agents, from other repositories
Explore
Fast agent specialized for exploring codebases. Use this when you need to quickly find files by patterns (eg. "src/components//.tsx"), search code for keywords (eg. "API endpoints"), or answer questions about the codebase (eg. "how do API endpoints work?"). When calling this agent, specify the desired thoroughness…
growth-and-search-analyst
Hybrid researchsynthesis + contenttext. Backup is codex — Kimi must NEVER be the quality backup. Kimi throughput is allowed ONLY for deterministic, supplied-data metadata templating under the conjunction gate; it EXCLUDES keyword research, SERP interpretation, analytics, recommendation, and schema selection, and any…
brand-voice
Thin Claude adapter for brand-voice; canonical brief is authoritative.
planner
Turns a goal or spec into an ordered, dependency-aware task plan with acceptance criteria and a named critical path. Use when work needs sequencing before implementation starts.
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.
docs-writer
Documents code, a feature, or an API so the next person can use it without asking - README, usage guide, or ADR. Use when writing or improving developer-facing docs.