Borrowing it
Nothing to install: this file belongs to lebek/modmixer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lebek/modmixer/main/.claude/commands/analyze-chat.mdgit clone --depth 1 https://github.com/lebek/modmixerWrote 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/commands/lebek/modmixer/analyze-chat)<a href="https://agentmods.dev/commands/lebek/modmixer/analyze-chat"><img src="https://agentmods.dev/badge/commands/lebek/modmixer/analyze-chat/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/commands/lebek/modmixer/analyze-chat"><img src="https://agentmods.dev/badge/commands/lebek/modmixer/analyze-chat.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.00024 | $0.00438 |
| Opus 5.5 | $0.00010 | $0.00175 |
| Sonnet 5.5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
analyze-chat 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.
What it actually says
/analyze-chat
Audit a ModMixer chat session. Goal: understand how the session went and what (if anything) the harness should change. You decide how to analyze and what to surface — pick the lens that fits what you actually see.
Lenses worth considering (non-exhaustive — use what fits):
- Agent intelligence — did the model understand the request, make good judgment calls, recover from mistakes?
- Token efficiency — where is context going, what's wasted, what could be smaller?
- Tool usage — right tool for the job, parallelism where possible, avoidable repeats or errors?
- Harness quality — system prompt, available tools, skills, hooks — anything missing or misfiring?
$ARGUMENTS — case-insensitive substring match against the conversation title or scope.modFolder. If empty, pick the conversation with the largest updatedAt.
Locate the session
The modmixer-artifacts skill describes the on-disk layout — invoke it if you need paths. Read $env:APPDATA\ModMixer\conversations.json (Windows). Schema: { conversations: [{ id, sessionFile, scope: {type, modFolder?}, title, updatedAt }], activeByMod }.
- No argument → largest
updatedAt. - With argument → substring match. If >1 match, list candidates with
updatedAtand stop. If 0, say so and stop.
The session file is JSONL and can be large — stream it with Node/Bash rather than Reading the whole thing into context.
Analyze and report
Up to you. Be concrete — cite tool-call indices, byte counts, turn numbers when they support a point. Skip sections that wouldn't add signal. Keep the report tight; if you're padding, stop.
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 · 31 lines · 24 tokens per session scan A d53a425c4241
analyze-chat is a command published in the GitHub repository lebek/modmixer (30 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 438 once invoked, about $0.0001 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 commands, from other repositories
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
branch-cleanup
Clean up merged and stale branches locally and remotely.
aidd-churn
Rank files by hotspot score to identify prime candidates for refactoring before PR review.
generate-docs
Generate or update project documentation including README, API docs, and changelog.
audit-accessibility
Audit web page or component for WCAG accessibility compliance.