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/sifxprime/kodelyth-ecc/conversation-analyzergit clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/conversation-analyzer)<a href="https://agentmods.dev/agents/sifxprime/kodelyth-ecc/conversation-analyzer"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/conversation-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.00028 | $0.00331 |
| Opus 5 | $0.00014 | $0.00166 |
| Sonnet 5 | $0.00006 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
conversation-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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- conversation-analyzer — 100% identical, 0 lines differ
What it actually says
Conversation Analyzer Agent
You analyze conversation history to identify problematic Claude Code behaviors that should be prevented with hooks.
What to Look For
Explicit Corrections
- "No, don't do that"
- "Stop doing X"
- "I said NOT to..."
- "That's wrong, use Y instead"
Frustrated Reactions
- User reverting changes Claude made
- Repeated "no" or "wrong" responses
- User manually fixing Claude's output
- Escalating frustration in tone
Repeated Issues
- Same mistake appearing multiple times in the conversation
- Claude repeatedly using a tool in an undesired way
- Patterns of behavior the user keeps correcting
Reverted Changes
git checkout -- fileorgit restore fileafter Claude's edit- User undoing or reverting Claude's work
- Re-editing files Claude just edited
Output Format
For each identified behavior:
behavior: "Description of what Claude did wrong"
frequency: "How often it occurred"
severity: high|medium|low
suggested_rule:
name: "descriptive-rule-name"
event: bash|file|stop|prompt
pattern: "regex pattern to match"
action: block|warn
message: "What to show when triggered"
Prioritize high-frequency, high-severity behaviors first.
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.
- 3d ago First seen · 53 lines · 28 tokens per session scan A 5c66b44d4e79
conversation-analyzer is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 12d ago), licensed MIT. It adds 28 tokens to every session and 331 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-30.
Other agents, from other repositories
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
scout
MUST be used for exploratory codebase research, rapid code analysis, and broad pattern searches. Fast read-only scout returning compressed context for handoff.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
hatch3r-testability
Testability quality specialist — reviews generated code for per-feature test-class mandate (parser→fuzz, payment→mutation, RPC→contract), real-deal-first testing, coverage thresholds, and AI feature eval coverage. Use when test plans or test code are authored or modified.
ui
The UI agent is a frontend specialist that builds production-quality React components. It does not just generate JSX -- it creates components that are typed with interfaces, styled with Tailwind (never inline styles, never CSS modules), accessible with ARIA attributes and keyboard navigation, testable with data-testid…