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/Jamie-BitFlight/claude_skillsWrote 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/jamie-bitflight/claude_skills/analyze)<a href="https://agentmods.dev/commands/jamie-bitflight/claude_skills/analyze"><img src="https://agentmods.dev/badge/commands/jamie-bitflight/claude_skills/analyze.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.1 | $0.00010 | $0.00445 |
| Opus 5 | $0.00005 | $0.00222 |
| Sonnet 5 | $0.00002 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00044 |
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 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
Run the autonomous transcript analysis pipeline. Spawn the @transcript-analyst agent to query JSONL session data, detect anti-patterns, and write structured findings.
Arguments
<user_arguments>$ARGUMENTS</user_arguments>
--project {project}— Scope analysis to a specific project. The project key is the path with hyphens replacing slashes. Default: current project (derived from cwd).--dimensions {dimensions}— Comma-separated list of dimensions to analyze. Options: tool-misuse, errors, tooling-gaps, delegation, shortest-path, red-herrings, interruptions, missing-hooks, all. Default: all.
Execution Steps
-
Resolve transcript path. Determine the project transcript directory:
~/.claude/projects/{project}/If
--projectis provided, use it as the project key. Otherwise, derive from the current working directory by replacing/with-and prepending-. -
Create output directory. Ensure
.planning/kaizen/exists in the current project root. -
Delegate the analysis via Agent tool:
subagent_type: agentskill-kaizen:transcript-analyst prompt: "Analyze transcripts at {path}. Dimensions: {dimensions}. Write findings to .planning/kaizen/analysis-{date}.md"The agent has access to DuckDB MCP for SQL queries and the custom kaizen MCP for process mining. Let it choose its own analysis approach.
-
Report results. After the agent completes, summarize:
- Number of sessions analyzed
- Number of findings by severity
- Path to the analysis report file
Output
Analysis report written to .planning/kaizen/analysis-{YYYY-MM-DD}.md with structured findings including session IDs, severity, evidence, and improvement recommendations.
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 · 45 lines · 10 tokens per session scan A 5a367d60aba2
analyze is a command published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 445 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.