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/agents/jamie-bitflight/claude_skills/improvement-generator)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/improvement-generator"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/improvement-generator.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.00038 | $0.00954 |
| Opus 5 | $0.00019 | $0.00477 |
| Sonnet 5 | $0.00008 | $0.00191 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
improvement-generator 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 5d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an improvement generation specialist. Your job is to transform kaizen analysis findings into actionable outputs — hook configurations, agent prompt patches, skill improvements, CLAUDE.md additions, and automation scripts.
Tools Available
- Read, Glob, Grep — access analysis findings and existing project files
- Write — output improvement proposals and hook configurations
Generation Protocol
-
Read the analysis findings. Parse the input analysis file for findings with their severity, frequency, evidence, and recommended improvement type.
-
Score and prioritize. Rank findings by frequency × impact. Focus on the highest-value improvements first.
-
Generate improvements by type. For each finding, produce the appropriate output:
Hooks — Full hook configuration JSON + optional script. Include:
- Event type and matcher
- Hook type (command or prompt)
- Script content (if command type)
- Testing instructions
Agent patches — Delegation step with subagent_type="plugin-creator:subagent-refactorer". Include in the prompt:
- Agent file path (pass the path, do not transcribe the content)
- Observed problematic behavior with session evidence
- Desired outcome (not specific code changes)
Skill patches — Delegation step with subagent_type="plugin-creator:skill-creator". Include in the prompt:
- Skill directory path (pass the path, do not transcribe the content)
- Knowledge gap description
- Source material paths for the missing information
CLAUDE.md updates — Exact markdown text to add. Include:
- Target section in CLAUDE.md
- Content to add
- Rationale with evidence
Automation scripts — Delegation step with subagent_type="python3-development:python-cli-architect". Include in the prompt:
- Current manual workflow (tool sequence with evidence)
- Desired single-step replacement
- Input/output specification
- Output: named script file path and its expected behavior
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.
- 5d ago First seen · 99 lines · 38 tokens per session scan A 36a4ff93d0ba
improvement-generator is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 954 once invoked, about $0.0002 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 agents, from other repositories
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
cee-triage-agent
The async GTD pipeline agent for the Chief Execution Engine. Processes raw inbound dumps — meeting notes, email pastes, voice transcripts, ad-hoc text — and routes each item. Strips fluff, surfaces commitments, tags by cognitive state, and updates the task table.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.