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/abossenbroek/abossenbroek-claude-pluginsWrote 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/abossenbroek/abossenbroek-claude-plugins/improve-plugin)<a href="https://agentmods.dev/commands/abossenbroek/abossenbroek-claude-plugins/improve-plugin"><img src="https://agentmods.dev/badge/commands/abossenbroek/abossenbroek-claude-plugins/improve-plugin/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/abossenbroek/abossenbroek-claude-plugins/improve-plugin"><img src="https://agentmods.dev/badge/commands/abossenbroek/abossenbroek-claude-plugins/improve-plugin.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.00687 |
| Opus 5.5 | $0.00000 | $0.00275 |
| Sonnet 5.5 | $0.00000 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
improve-plugin 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 2mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/improve-plugin Command
Improve an existing Claude Code plugin with SOTA context engineering patterns.
Usage
/improve-plugin [focus] [path]
Arguments
focus (optional):
all- Full improvement pass (context + orchestration + handoff) (default)context- Optimize context management (Four Laws)orchestration- Improve agent hierarchy and coordinationhandoff- Optimize agent-to-agent data transfer
path (optional):
- Path to plugin directory (default: auto-detect in current workspace)
Instructions
You are the MINIMAL entry point for plugin improvement. Your ONLY job is to:
- Parse focus and path arguments
- Locate the plugin to improve
- Launch the improve-coordinator agent
- Return the coordinator's output directly
Step 1: Parse Arguments
Determine focus area and plugin path:
- Default focus:
all - Default path: Look for
.claude-plugin/plugin.jsonin workspace
Step 2: Locate Plugin
If no path provided:
- Search for
.claude-plugin/plugin.jsonfiles - If multiple found, ask user to specify
- If none found, ask user to provide path
Verify the plugin exists by checking for plugin.json.
Step 3: Launch Coordinator
Use the Task tool to launch the improve-coordinator agent:
Task: Improve plugin with SOTA patterns
Agent: agents/improve-coordinator.md
Prompt:
plugin_path: [resolved plugin directory]
focus_area: [parsed focus: all|context|orchestration|handoff]
The coordinator will:
- Analyze the plugin structure
- Generate improvements based on focus area
- Ground improvements (pattern check, token estimate, risk)
- Present options for user selection
- Generate final improvement report
Step 4: Return Output
Return the coordinator's improvement report DIRECTLY to the user.
DO NOT:
- Add commentary about the process
- Explain what the coordinator did
- Include intermediate analysis
- Modify the report in any way
ONLY return the final improvement report.
Context Isolation Rules
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.
- 2mo ago First seen · 121 lines · 0 tokens per session scan A 4c9365d649e3
improve-plugin is a command published in the GitHub repository abossenbroek/abossenbroek-claude-plugins (2 stars, last pushed 6mo ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 687 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.
improve-plugin compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| improve-pluginabossenbroek/abossenbroek-claude-plugins | Command | 2 | 6mo ago | BSD-3-Clause | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | today | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | today | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | today | MIT | A | 13 | Claude Code |
| convergegithub/spec-kit | Command | 148k | today | MIT | A | 35 | Claude Code |
| speckit.bug.testgithub/spec-kit | Command | 148k | today | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | today | MIT | A | 26 | Claude Code |