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/DennisLiuCk/claude-plugin-marketplaceWrote 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/dennisliuck/claude-plugin-marketplace/log-analyzer)<a href="https://agentmods.dev/agents/dennisliuck/claude-plugin-marketplace/log-analyzer"><img src="https://agentmods.dev/badge/agents/dennisliuck/claude-plugin-marketplace/log-analyzer/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/dennisliuck/claude-plugin-marketplace/log-analyzer"><img src="https://agentmods.dev/badge/agents/dennisliuck/claude-plugin-marketplace/log-analyzer.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.00123 | $0.03616 |
| Opus 5.5 | $0.00049 | $0.01446 |
| Sonnet 5.5 | $0.00025 | $0.00723 |
| Haiku 4.5 | $0.00012 | $0.00362 |
Grade A, and why
log-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 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 First seen · 380 lines · 123 tokens per session scan A 72b76f2dabb3
log-analyzer is an agent published in the GitHub repository DennisLiuCk/claude-plugin-marketplace (27 stars, last pushed 7mo ago), with no licence file. It adds 123 tokens to every session and 3,616 once invoked, about $0.0005 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-30.
Other agents, from other repositories
diagnostician
Specialized root cause debugger. Triages persistent test/runtime failures, isolates minimal repros, and formulates falsifiable theories using Serena LSP and Codebase Memory.
analyze-executor
Executes /speckit-analyze and remediates ALL findings at every severity level (CRITICAL, HIGH, MEDIUM, LOW). After running the analysis, this agent fixes each finding, researching with web search, library docs, codebase exploration, and local file analysis whatever current evidence does not settle, then applies the…
graph-analyst
Analyzes the dependency graph to identify structural risks like high fan-out, central nodes, and import cycles.
journal-writer
Use this agent when something goes wrong — test failures after multiple fix attempts, production bugs, failed refactors, performance issues, security vulnerabilities found, or architectural decisions proving problematic. Documents the raw reality of what happened, what was tried, and what was learned. Use proactively…
bug-analyzer
Analyze root cause of bugs after location is identified. Second step in bug investigation.
lateralus-workaround
Makeshift bypass generator. Gets the user unblocked without fixing root cause. Use when horizon is demo, deadline, POC, test, or just-need-to-move. Always produces a debt log. Never dresses up a bypass as a real fix.