Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/josix/agent-flownpx agentmods add commands/josix/agent-flow/analyzeWrote 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/josix/agent-flow/analyze)<a href="https://agentmods.dev/commands/josix/agent-flow/analyze"><img src="https://agentmods.dev/badge/commands/josix/agent-flow/analyze/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/josix/agent-flow/analyze"><img src="https://agentmods.dev/badge/commands/josix/agent-flow/analyze.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.00000 | $0.01065 |
| Opus 5.5 | $0.00000 | $0.00426 |
| Sonnet 5.5 | $0.00000 | $0.00213 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
analyze 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Command
Parse Claude Code session transcripts offline and surface subagent behavior metrics, tool usage patterns, token costs, and improvement opportunities — all stored in a local SQLite database with no network calls.
Arguments
--all-sessions(default for first run): Load all sessions from the auto-detected transcripts directory--session <id>: Restrict loading to one session UUID--report: Generate a full markdown report (default action after loading)--sessions: List loaded sessions with event counts--sql <query>: Run ad-hoc SQL against the events database--transcripts-dir <path>: Override the auto-detected transcripts directory--db <path>: Override the database path (default:.claude/observability/events.db)--redact: Mask credential patterns (AWS keys, OpenAI keys, GitHub PATs) before storing
Workflow
FIRST RUN — Load transcripts and generate a report:
bash scripts/analyze.sh load --all-sessions
bash scripts/analyze.sh report
Or as a two-step invocation:
bash scripts/analyze.sh load --all-sessions && bash scripts/analyze.sh report
Inspect sessions:
bash scripts/analyze.sh sessions
Ad-hoc SQL:
bash scripts/analyze.sh sql "SELECT agent_type, COUNT(*) FROM events GROUP BY agent_type"
What You'll See
Report Sections
| Section | Description |
|---|---|
| Session Overview | All loaded sessions with timestamps, branch, event count, subagent count |
| Tool Usage by Agent | Which tools each agent called and how often |
| Skill / MCP Invocations | MCP tool calls per agent (graphify, personal-kb, etc.) |
| Thinking Effort | Thinking block count and character totals by agent |
| Token Usage | Input/output/cache tokens by agent and model |
| Subagent Dispatches & Iteration Rate | How many times each subagent type was dispatched per session |
| Rejection Rate | Stop-hook block/approve/deny decisions per agent |
| Improvement Opportunities | Automated heuristics (see below) |
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 · 134 lines · 0 tokens per session scan A e8a024e4b5d3
analyze is a command published in the GitHub repository josix/agent-flow (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,065 tokens. 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 commands, from other repositories
security-scan
Run AgentShield against agent, hook, MCP, permission, and secret surfaces.
learn
Extract patterns and learnings from current session.
export-closedloop-learnings
Exports pending ClosedLoop learnings to global location with deduplication.
help
Quick reference for all Attune commands.
pm-roadmap
Generate or update the product roadmap. Spawns roadmap-planner. Outputs themed roadmap (Now / Next / Later) with rationale per theme.
t00-status
A status-report command for a T00 task workspace, using files that record communication, tasks, and the previous session's next steps.