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.
npx skills add ToruAI/toru-claude-agents --skill self-improvementgit clone --depth 1 https://github.com/ToruAI/toru-claude-agentsWrote 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/skills/toruai/toru-claude-agents/self-improvement)<a href="https://agentmods.dev/skills/toruai/toru-claude-agents/self-improvement"><img src="https://agentmods.dev/badge/skills/toruai/toru-claude-agents/self-improvement/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/skills/toruai/toru-claude-agents/self-improvement"><img src="https://agentmods.dev/badge/skills/toruai/toru-claude-agents/self-improvement.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.00675 |
| Opus 5 | $0.00012 | $0.00338 |
| Sonnet 5 | $0.00005 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
self-improvement 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 11d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-Improvement Protocol
You are responsible for making yourself and the system better over time.
The Improvement Loop
1. NOTICE - Identify friction, repetition, or failure
2. ANALYZE - Why did this happen? What's the root cause?
3. DESIGN - What's the minimal fix?
4. IMPLEMENT - Create skill/hook/agent update
5. TEST - Verify it works
6. DOCUMENT - Log in megg
7. SHARE - Tell the user if significant
What to Improve
Process Friction
- Repeated manual steps → automate with hooks
- Same context loading → create skill
- Unclear delegation → improve agent descriptions
- Lost decisions → strengthen megg discipline
Quality Issues
- Bugs that reach review → add validation hooks
- Incomplete work → improve checklists in skills
- Scope creep → add explicit boundaries
- Vision drift → strengthen context protocols
Efficiency
- Slow operations → use subagents for parallel work
- Context bloat → progressive disclosure in skills
- Repeated research → cache in megg or skill
When to Improve
After every significant task:
- What went well?
- What was harder than expected?
- What would I do differently?
When you notice:
- Same thing done 3+ times → automate
- Decision made twice → document
- Error repeated → add guard
Periodically:
- Review megg decisions - patterns?
- Check skills - still accurate?
- Audit hooks - still needed?
Where to Put Improvements
| Scope | Location | When |
|---|---|---|
| Personal | ~/.claude/skills/ |
Your workflows only |
| Project | .claude/skills/ |
Team needs it |
| System | Update agent definitions | Core behavior change |
Documentation Pattern
When creating improvement, log it:
## YYYY-MM-DD - Improvement: [Name]
**Friction:** What problem was encountered
**Root Cause:** Why it happened
**Solution:** What was created/changed
**Location:** Where the fix lives
**Verification:** How to know it works
Improvement Ideas Backlog
When you notice something but can't fix now:
- Add to
~/.claude/skills/self-improvement/ideas.md - Include: friction, proposed fix, priority
- Review periodically
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.
- 11d ago First seen · 106 lines · 24 tokens per session scan A b5384b36e0a4
self-improvement is a skill published in the GitHub repository ToruAI/toru-claude-agents (15 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 675 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-08-30.
Other skills, from other repositories
skill-factory
A workflow that examines completed session work and turns reusable patterns into Claude Code skills.
session-wrap
Use when wrapping up a session before ending. 4 parallel subagents detect doc updates, repeated patterns, learning points, and follow-ups, then a verifier deduplicates and presents choices. Triggers on /session-wrap, session wrap, session cleanup, end of session.
skill-creator
Create new skills (SKILL.md files), modify and improve existing skills, and design skill descriptions for accurate triggering. Use when the user wants to create a new skill from scratch, edit an existing skill, optimize a skill's description, or convert a workflow they just demonstrated into a reusable skill.
memstack-automation-n8n-workflow-builder
Use this skill when the user says 'n8n workflow', 'build a workflow', 'automation workflow', 'connect services', or needs visual workflow design with node mapping, data transformations, and error handling for n8n. Do NOT use for standalone webhook endpoints or cron jobs.
relay
Session relay — compresses what's been done so far (writes a one-liner for /compact) and generates a "next task" prompt (a baton) for the user to hand off. Use on requests like "relay / hand off / next session / continue after compact / baton / handoff / clean up context and continue next task." Does not run /compact…
template-engine
Load, validate, and populate templates consistently across frameworks.