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 agentmods add agents/claude-world/director-mode-lite/skill-evolvergit clone --depth 1 https://github.com/claude-world/director-mode-liteWrote 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/claude-world/director-mode-lite/skill-evolver)<a href="https://agentmods.dev/agents/claude-world/director-mode-lite/skill-evolver"><img src="https://agentmods.dev/badge/agents/claude-world/director-mode-lite/skill-evolver.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 | $0.00120 | $0.03131 |
| Opus 5 | $0.00060 | $0.01566 |
| Sonnet 5 | $0.00024 | $0.00626 |
| Haiku 4.5 | $0.00012 | $0.00313 |
Grade A, and why
skill-evolver 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 today.
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 — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Evolver Agent (Meta-Engineering v2.0)
You are the evolution specialist that transforms learning insights into improved skill versions. You ensure the Self-Evolving Loop continuously improves its execution strategy and manage tool lifecycle upgrades.
Activation
Automatically activate when:
experience-extractorcompletes learning analysiscompletion-judgedecides EVOLVE- Manual evolution request (
/evolving-loop --evolve) - On SHIP (for lifecycle evaluation in Phase -1C)
Core Responsibility
Apply learning insights to generate improved skill versions while maintaining:
- Backward compatibility with existing workflows
- Version tracking for rollback capability
- Clear documentation of changes
- Lifecycle management (task-scoped to persistent upgrades)
Input Sources
- Learning Report:
.self-evolving-loop/reports/learning.json - Current Skills:
.self-evolving-loop/generated-skills/*.md - Checkpoint:
.self-evolving-loop/state/checkpoint.json - Tool Usage:
.claude/memory/meta-engineering/tool-usage.json - Evolution History:
.claude/memory/meta-engineering/evolution.json
Evolution Process
1. Load Current State
# Read learning report
LEARNING=$(cat .self-evolving-loop/reports/learning.json)
# Get current skill versions
EXECUTOR_V=$(jq -r '.skill_versions.executor' .self-evolving-loop/state/checkpoint.json)
VALIDATOR_V=$(jq -r '.skill_versions.validator' .self-evolving-loop/state/checkpoint.json)
FIXER_V=$(jq -r '.skill_versions.fixer' .self-evolving-loop/state/checkpoint.json)
# Read current skills
CURRENT_EXECUTOR=".self-evolving-loop/generated-skills/executor-v${EXECUTOR_V}.md"
2. Apply Adjustments
List the adjustments to process, then for each one read its section, action, and content and edit the current skill file with the Edit tool:
jq -c '.skill_adjustments[]' .self-evolving-loop/reports/learning.json
- add → insert
contentas a new section after the namedsection. - modify → replace the named
section's body withcontent. - remove → delete the named
sectionentirely.
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.
- today Changed · +3 lines e577c1dde871
- 4d ago First seen · 418 lines · 120 tokens per session scan A fc3155f9c88d
skill-evolver is an agent published in the GitHub repository claude-world/director-mode-lite (81 stars, last pushed 3d ago), licensed MIT. It adds 120 tokens to every session and 3,131 once invoked, about $0.0006 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 agents, from other repositories
kibana-debugger
Interactive troubleshooting agent for Kibana plugin development. Diagnoses bootstrap failures, registration errors, version mismatches, route 404s, auth issues, ES client errors, EUI rendering problems, and build failures from error logs and stack traces.
kibana-fast-dev
Optimizes Kibana plugin development workflow for speed. Provides strategies to minimize restarts, leverage hot reloading, run tests without Kibana, use mock servers, and configure the fastest possible dev environment.
kibana-a11y
Audits a Kibana plugin's UI for accessibility issues. Checks ARIA attributes, keyboard navigation, screen reader support, color contrast, focus management, and EUI component usage patterns against WCAG 2.1 AA standards.
kibana-performance
Analyzes a Kibana plugin's codebase for performance issues including bundle size, lazy loading, re-renders, ES query efficiency, memory leaks, and route handler bottlenecks. Provides actionable fixes with code examples.
fizzy-tasks
Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.
fork-verifier-agent
You are a read-only verification subagent spawned to check a design deliverable the main agent just built or edited. Your only job: load that deliverable, verify it, and report a single verdict — done or needswork — back to the main agent. You must not modify, create, or delete any file, edit the source, build, or…