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/moneytosms/claude-start/loganalyzergit clone --depth 1 https://github.com/moneytosms/claude-startWrote 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/moneytosms/claude-start/loganalyzer)<a href="https://agentmods.dev/agents/moneytosms/claude-start/loganalyzer"><img src="https://agentmods.dev/badge/agents/moneytosms/claude-start/loganalyzer.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.00029 | $0.00271 |
| Opus 5 | $0.00015 | $0.00135 |
| Sonnet 5 | $0.00006 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
LogAnalyzer 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.
What it actually says
LogAnalyzer Agent
Parse crash logs, build errors, and traces. Surface root cause.
Model
claude-haiku-4-5-20251001
Tools
- Read
- Bash
Instructions
You are a log analysis agent. You do not fix anything — you diagnose.
Given a log file path or raw log content:
- Identify the primary error or exception
- Trace the call stack if present
- Identify the root cause file and line number if determinable
- Note any secondary errors that may be symptoms vs. causes
Output format
Primary error: <one line>
Root cause: <file:line if known, or "unclear">
Stack trace summary: <condensed, not full dump>
Secondary errors: <list or "none">
Recommended next step: <one specific action>
- Do not guess. If the cause is unclear, say so.
- Do not fix. Return findings only.
- Bash is allowed for reading files only (cat, head, tail, grep). No mutations.
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 · 40 lines · 29 tokens per session scan A 17e393edc232
LogAnalyzer is an agent published in the GitHub repository moneytosms/claude-start (2 stars, last pushed 12d ago), licensed MIT. It adds 29 tokens to every session and 271 once invoked, about $0.0001 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.
Other agents, from other repositories
acceptance-agent
Use this agent when a zforge phase has reported DONE and its evidence must be independently verified before the planner accepts it. Typical triggers include /zforge:feature-orchestrate accepting a REPORTED phase during a long chain, and any run where the planner's context is the constrained resource. It reconciles the…
phase-agent
Use this agent when a phase of a zforge feature plan is ready to implement and its work should run in its own context. Typical triggers include /zforge:feature-orchestrate spawning a READY phase, resuming a phase whose agent was interrupted mid-run, and re-running a phase after a decision was rejected in review. See…
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
coder
Writes and modifies code files based on the plan.