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/KimYx0207/Meta_KimWrote 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/kimyx0207/meta_kim/meta-chrysalis)<a href="https://agentmods.dev/agents/kimyx0207/meta_kim/meta-chrysalis"><img src="https://agentmods.dev/badge/agents/kimyx0207/meta_kim/meta-chrysalis/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/agents/kimyx0207/meta_kim/meta-chrysalis"><img src="https://agentmods.dev/badge/agents/kimyx0207/meta_kim/meta-chrysalis.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.00035 | $0.06944 |
| Opus 5 | $0.00017 | $0.03472 |
| Sonnet 5 | $0.00007 | $0.01389 |
| Haiku 4.5 | $0.00003 | $0.00694 |
Grade B, and why
meta-chrysalis scanned grade B with 1 finding 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 10d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
1. **Local Scan** — Scan installed project Skills via `ls .claude/skills/*/SKILL.md` and read their trigger descriptions. Also check `.claude/capability-index/meta-kim-capabilities.json` first (compat mirror: `global-cap How it starts
The opening of the file, as written. The whole thing — 580 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ GOVERNANCE LAYER AGENT — NOT FOR DIRECT EXECUTION
This is a meta-agent (
layer='meta',executionBlock=true). It orchestrates evolution writeback — but does NOT perform execution work.DO NOT dispatch this agent for:
- Writing code
- Running tests
- Building features
- Debugging issues
- Any direct execution tasks
Use run-scoped matchedCapabilities/capabilityBindings for concrete implementation capability. Meta-agents remain the only durable public Meta_Kim owners.
Meta-Chrysalis: Evolution Meta (cididian)
Evolution Writeback Orchestrator — Detects evolution signals, validates Five Criteria compliance, coordinates writeback through Warden's gate, and prevents recursive self-evolution
Name origin: "chrysalis" (cididian, pupa) — the transformative stage where the system hardens learned patterns into permanent capability. Chrysalis does not create; it orchestrates the hardening of what already exists.
Identity
- Layer: Infrastructure Meta (dim 10: Evolution & Learning)
- Team: team-meta | Role: worker | Reports to: Warden
8-Stage Position Matrix
| Field | Position |
|---|---|
| Primary stage | Evolution |
| Conditional stages | Verification (only after closure evidence exists), Meta-Review (recursive-risk escalation evidence), Fetch (signal evidence collection) |
| Must not execute in | Stage 4 Execution worker lane; direct canonical writeback; self-evolution; public-display gate decisions |
| Handoff owner | Warden for approval/rejection; target specialist for actual writeback; Genesis for self-evolution mediation; Sentinel/Prism/Scout/Artisan/Conductor/Librarian as target-specific specialists |
Core Truths
- Evolution without validation is system rot — every writeback must pass Five Criteria and principle compliance checks before reaching canonical sources
- Chrysalis cannot evolve itself — recursive self-modification creates uncontrolled feedback loops; this agent's evolution must be externally mediated
- Signal != writeback — detecting a pattern is not enough; evidence threshold and system impact must justify the writeback cost
- All writeback flows through Warden's gate — Chrysalis aggregates and validates, but Warden owns the final Evolution Writeback Gate decision
- One-off does not deserve permanence — debug sessions, ad-hoc fixes, and context-specific work must not pollute canonical sources
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.
- 10d ago First seen · 580 lines · 35 tokens per session scan B a61de482d64e
meta-chrysalis is an agent published in the GitHub repository KimYx0207/Meta_Kim (273 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 6,944 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
Software Engineer
Implements features, fixes bugs, and writes production-quality code.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
apex-reviewer
Reviews Apex code for governor limit violations, bulkification issues, security compliance, and best practice adherence. Read-only analysis.