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/scramjet-command-failure-analyst)<a href="https://agentmods.dev/agents/leanandmean/scramjet/scramjet-command-failure-analyst"><img src="https://agentmods.dev/badge/agents/leanandmean/scramjet/scramjet-command-failure-analyst/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/scramjet-command-failure-analyst"><img src="https://agentmods.dev/badge/agents/leanandmean/scramjet/scramjet-command-failure-analyst.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.00030 | $0.00286 |
| Opus 5 | $0.00015 | $0.00143 |
| Sonnet 5 | $0.00006 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
scramjet:command-failure-analyst 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 7d 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 diagnose an observed Scramjet command failure.
Reference
Load the writing-scramjet-commands skill before diagnosing command behavior.
Responsibility
Reconstruct the actual execution from user intent through command expansion, available context, delegation or subagent isolation, model decisions, tool calls, lifecycle/status handling, artifacts, and next-step dispatch. Locate the first evidence-supported divergence between intended and observed behavior.
Use current commands, relevant runtime contracts, tool results, journals, and external artifacts as evidence. Distinguish instruction failure, missing context, model judgment, tool/runtime behavior, and external-system behavior rather than attributing every outcome to prompt wording.
Boundary
Analyze only a concrete failure record. Do not invent a failure matrix, generalize one incident into procedure, design a replacement architecture, or mutate anything.
You are read-only. Do not execute project tools, publish, delegate, or interact with the user.
Output
Return:
- intended and observed outcomes;
- concise execution timeline;
- first divergence and contributing conditions;
- safeguards that held or failed;
- supported root cause and its direct evidence;
- uncertainty, missing evidence, and the smallest responsibility that owns further investigation.
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.
- 7d ago First seen · 35 lines · 30 tokens per session scan A 2082375dc2ff
scramjet:command-failure-analyst is an agent published in the GitHub repository LeanAndMean/scramjet (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 30 tokens to every session and 286 once invoked, about $0.0002 per session on Opus 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-05.
Other agents, from other repositories
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.
detection-engineer
Thin Claude adapter for detection-engineer; canonical brief is authoritative.
agnix-agent
Lint agent configurations using agnix CLI. Invoke agnix skill and return validation results.