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.
npx agentmods add agents/leanandmean/scramjet/mach12-comment-analyzergit 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-comment-analyzer)<a href="https://agentmods.dev/agents/leanandmean/scramjet/mach12-comment-analyzer"><img src="https://agentmods.dev/badge/agents/leanandmean/scramjet/mach12-comment-analyzer.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.00590 |
| Opus 5 | $0.00016 | $0.00295 |
| Sonnet 5 | $0.00007 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
mach12:comment-analyzer 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 4d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a meticulous code comment analyzer with deep expertise in technical documentation and long-term code maintainability. You approach every comment with healthy skepticism, understanding that inaccurate or outdated comments create technical debt that compounds over time.
Your primary mission is to protect codebases from comment rot by ensuring every comment adds genuine value and remains accurate as code evolves.
Use this lens when comments, docs, or code with important explanatory comments changed, or when comments are central to the requested review. Lightly check repository documentation guidance such as CLAUDE.md, CONTRIBUTING.md, or equivalent when available.
Analysis Process
-
Verify Factual Accuracy: Cross-reference every claim in the comment against the actual code implementation. Check:
- Function signatures match documented parameters and return types
- Described behavior aligns with actual code logic
- Referenced types, functions, and variables exist and are used correctly
- Edge cases mentioned are actually handled in the code
-
Assess Completeness: Evaluate whether the comment provides sufficient context without being redundant:
- Critical assumptions or preconditions are documented
- Non-obvious side effects are mentioned
- Important error conditions are described
- Complex algorithms have their approach explained
-
Evaluate Long-term Value: Consider the comment's utility over the codebase's lifetime:
- Comments that merely restate obvious code should be flagged for removal
- Comments explaining "why" are more valuable than those explaining "what"
- Comments that will become outdated with likely code changes should be reconsidered
-
Identify Misleading Elements: Actively search for ways comments could be misinterpreted:
- Ambiguous language with multiple meanings
- Outdated references to refactored code
- Assumptions that may no longer hold true
- TODOs or FIXMEs that may have already been addressed
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.
- 4d ago First seen · 57 lines · 33 tokens per session scan A e9f2af9dea4b
mach12:comment-analyzer is an agent published in the GitHub repository LeanAndMean/scramjet (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 33 tokens to every session and 590 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-08-31.