EvoKernel
Deterministic Self-Evolving Meta-Kernel for AI Coding Agents — Offline Git Worktree Evolution, Zero-Dep Deliverable Inspector, AST Cognitive Memory & 5-Tool Meta-MCP Gateway
Install / Use
claude mcp add damonless -- npx -y github:damonless/EvoKernelIf the server publishes to npm under a different name, use that package instead — check the repo README.
MCP Server
Model Context Protocol server
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of EvoKernel
EvoKernel scores 83/100 on our quality scale, 2986th of 4,698 Development & Engineering skills we index.
Its MCP Server is 32 KB long, well organised into 44 sections with 10 code examples: a thorough specification that gives an agent plenty to work with.
It has 3 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated 2 days ago, so EvoKernel is actively maintained.
- Our last check on 2026-11-12 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-10. Automated pattern scan on 2026-11-09. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
EvoKernel compared with similar skills
All 4 of these similar skills score higher than EvoKernel; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| EvoKernel (this skill)by damonless | 83 | 3 | 2d ago | MCP Server |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install EvoKernel?
- Run
claude mcp add damonless -- npx -y github:damonless/EvoKernel. The install tabs above show the steps for each supported agent. - Which AI agents does EvoKernel work with?
- It is written for Claude Code, Claude Desktop, Cursor, Windsurf, Gemini CLI and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
- Is EvoKernel safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is EvoKernel still maintained?
- The repository was last updated 2 days ago, so EvoKernel is actively maintained.
Skill content
View source on GitHub🧬 EvoKernel (evo-kernel)
Cut MCP Tool Schema Tax by 94.4% (and Static Prefix Tax by 88.7%). Keep 100% KV Cache Hit. Evolve AST-Verified Memories & Sandboxed Tools in Isolated Git Worktrees — with Zero External Dependencies.
The Deterministic Self-Evolving Meta-Kernel & Cognitive Context OS for AI Coding Agents
Claude Code · Cursor · Codex · Windsurf · Cline · Roo · GitHub Copilot · OpenCode · Gemini · Antigravity
English · 简体中文 · 🌐 Live Workbench 2.0 · 📊 Benchmarks
<br/><a href="https://damonless.github.io/EvoKernel/"><img src="./assets/hero-shotcraft.svg" alt="EvoKernel 3-Tier Context OS & Benchmark Telemetry" width="100%" /></a>
</div>What is EvoKernel? EvoKernel stops your AI coding agent from repeating the same bugs across sessions — crystallizing root-cause fixes into code-anchored memories and sandboxed micro-tools, while folding bloated MCP schemas & rules behind 5 fixed primitives (-88.7% to -94.4% prompt tax, 100% KV cache hit, 0 external dependencies).
[!NOTE] Disambiguation Note: EvoKernel (
evo-kernel) is an agent architecture and context engineering framework for AI coding assistants (Claude Code, Cursor, Windsurf, Codex, Gemini, etc.). It is not affiliated with academic ICML papers/benchmarks of similar naming or Linux kernel projects.
⚡ 30-Second Quick Start
Get started in 3 commands — zero installation required:
# 1. Instant Zero-Write X-Ray (<25ms) — scan host rules, git hotspots & memory coverage
npx -y evo-kernel score
# 2. One-Click Safe Wiring & Doctor Check — wire 10 IDEs safely with stealth mode
npx -y evo-kernel init --stealth && npx -y evo-kernel doctor
# (Preview MCP virtualization token savings safely with: npx -y evo-kernel virtualize --dry-run)
# 3. Launch Workbench 2.0 & Verify Deliverables (.xlsx, .docx, .pptx, .csv, .json, .md)
npx -y evo-kernel ui --app
npx -y evo-kernel check ./README.md
<div align="center"> <img src="./assets/quickstart-shotcraft.svg" alt="EvoKernel 30-Second Quick Start Pipeline" width="100%" /> </div> <br/> <table> <tr> <td align="center" width="56%"> <b>EvoKernel Workbench 2.0 (<code>npx evo-kernel ui --app</code>)</b><br/> <a href="https://damonless.github.io/EvoKernel/"><img src="./assets/workbench-showcase.svg" width="100%" alt="EvoKernel Workbench 2.0 Zinc Dark Cockpit and AST Topology" /></a> </td> <td align="center" width="44%"> <b>Instant Terminal X-Ray (<code>npx evo-kernel score</code>)</b><br/> <img src="./assets/terminal-score-xray.svg" width="100%" alt="EvoKernel Terminal Score X-Ray Card" /> </td> </tr> </table> <details> <summary><b>🛠️ Clone from Source & Advanced CLI Workflows (Click to expand)</b></summary>💡 Node.js 18 / 20 Instant 1-Liner (No Global Node Upgrade Needed):
npx -y -p node@22 evo-kernel score
(Note:npx -p node@22is recommended for one-off CLI diagnostics. For a persistent background MCP service, upgrade system Node to>= 22.5.0vianvm install 22 && nvm use 22orfnm use 22, and install globally vianpm install -g evo-kernel.)
Why Node.js >= 22.5.0? EvoKernel runs purely on nativenode:sqlite,node:module, andnode:test— providing 0 external npm dependencies and 0 supply-chain vulnerability risk.
# Clone and build from source (takes <50ms, zero npm install required)
git clone https://github.com/damonless/EvoKernel.git
cd EvoKernel
node ./scripts/build.mjs
# Wire L0 Meta-Rule Seed + Single Meta-MCP into your active coding agents
node ./dist/cli/index.js init --targets auto --stealth
# Cold-start mine your repository structure, project stacks & Git fix history
node ./dist/cli/index.js bootstrap --max-commits=50
# Run offline worktree optimization cycle
node ./dist/cli/index.js optimize --dim both -k 3
# Inspect capability tree, multi-branch AST memory freshness & ROI ledger
node ./dist/cli/index.js tree
node ./dist/cli/index.js memory verify
node ./dist/cli/index.js stats
node ./dist/cli/index.js audit --global
node ./dist/cli/index.js doctor
</details>
🔒 Reversibility, Team Sharing & Privacy
EvoKernel is designed from the ground up to be safe to trial, transparent to inspect, and completely reversible at any moment:
1. What evo init Touches & 1-Command Lossless Uninstall
When you run npx evo-kernel init, it touches only three isolated surfaces:
- Host Agent Rule Files: Inserts a compact, bounded managed block between
<!-- EVO:START -->and<!-- EVO:END -->markers in detected configuration files (CLAUDE.md,AGENTS.md,GEMINI.md,.cursor/rules/evo-kernel.mdc). Existing user rules outside these markers are untouched. - Host MCP Configs: Registers a single stdio gateway entry for
evo-kernel(leaving third-party servers untouched unless virtualized). - Workspace
.evo/Tree: Generates local capability and episodic memory directories (.evo/rules/,.evo/skills/,.evo/memories/,.evo/tools/,.evo/.cache/).
To cleanly and completely revert your repository and agent configurations back to baseline, run:
npx -y evo-kernel virtualize --restore && npx -y evo-kernel uninstall
This restores any virtualized MCP servers to host configuration files, strips all <!-- EVO:START --> blocks cleanly, unwires registered lifecycle hooks, and removes .evo/ with zero left-behind configuration artifacts.
2. Multi-Person Team Sharing vs. --stealth Mode
- Multi-Person Team Sharing (Default
evo init): Commit.evo/rules/,.evo/memories/, and.evo/tools/to your Git repository. Every team member and coding agent immediately benefits from shared root-cause bug fixes and verified sandboxed micro-tools, while internal cache files (.evo/.cache/) are automatically gitignored. - Personal Standalone Trial (
evo init --stealth): Appends.evo/and modified host rule files to.git/info/exclude. Git completely ignores EvoKernel files locally without touching.gitignoreor creating uncommitted working tree diffs in shared repositories. Zero git pollution.
3. 100% Local-First & Zero Outbound Telemetry
EvoKernel performs 0 outbound network requests, transmits 0 analytics or telemetry, and requires 0 external cloud APIs. All SQLite FTS5 indexes and observable recall ledgers (.evo/.cache/telemetry.db) are stored 100% locally on your machine.
📈 50-Turn Context-Tax Analytical Model & Live Engine Micro-Benchmark (npm run benchmark)
Analytical cost/cache model across 8 standard MCP servers (github, playwright, kubernetes, docker, linear, postgres, sentry, context7 — 77 tools total) + a mature repo knowledge base (10 rules, 4 skills, 5 micro-tools, 15 debugging memories) over a 50-turn coding session with 3 mid-session capability evolutions, paired with live local engine micro-benchmarks (reproduce locally via npm run benchmark).
Note on zero-prefix-invalidation condition: The 0 mid-session cache invalidation guarantee holds when new capabilities are crystallized as core: false scoped rules, skills, micro-tools, or memory entries (the default in EvoKernel), which reside in .evo/ without mutating the top-level tools/list schema or host CLAUDE.md L0 prefix.
| Metric | Raw Multi-MCP + Monolithic CLAUDE.md | 🧬 EvoKernel 5-Tool Meta-Gateway | Model / Live Result |
| :--- | :---: | :---: | :---: |
| Exposed Tool Schemas | 77 tools | 5 fixed meta-tools | -93.5% schema footprint |
| MCP Tool Schema Tax / Turn | 27,150 tokens | 1,530 tokens | -94.4% MCP schema tax |
| 8-Server Full Static Prefix / Turn | 27,150 tokens | 3,066 tokens | -88.7% static prefix reduction |
| Mid-Session Cache Invalidations | 3 full prefix busts | 0 (100% cache hit) | 100% KV Cache Shield |
| 50-Turn Cumulative Prompt Tokens | 1,931,250 tokens | 738,570 tokens | -61.8% total token load |
| 50-Turn Cost (Claude Sonnet 4.5) | $1.15 | $0.34 | -70.4% API cost |
| 50-Turn Cost (Claude Opus 4.5) | $5.76 | $1.70 | -70.4% API cost |
| Live Engine AST Verification Speed | Unverified text (drifts silently) | ~0.32 ms / memory | <11ms batch across 34 memories¹ |
¹ Terminology Note: AST Anti-Drift / AST Fingerprinting utilizes Zero-Dep Lexical-Structural Skeleton Fingerprinting, which is immune to comments, code reformatting, and line-number drift without requiring external compiler dependencies.
⚡ Why Most "Self-Improving Agent" Setups Fail After 30 Sessions
Every developer using Claude Code, Cursor, Windsurf, Cline, Roo, Copilot, Codex, OpenCode, Gemini, or Antigravity hits five engineering walls:
- The Slop-Pile Rule Rot (
CLAUDE.mdBloat): Appending"Never do X"every time an agent makes a mistake turns your rules file into a 10,000-token contradictory junk drawer. Past ~1,500 tokens, LLM instruction-following degrades sharply (Lost-in-the-Middle). - Worker Grading Its Own Homework: Letting an LLM directly overwrite global skills or scripts without deterministic verification leads to broken, path-hardcoded scripts being crystallized as "permanent tools."
- The Dynamic MCP Prompt-Cache Collapse: If "evolving MCP tools" means spawning new MCP servers or mutating the top-level
tools/listschema mid-session, you invalidate the LLM's KV Prompt Cache prefix on every mutation—increasing token costs by 5–10x and requiring constant IDE restarts. - Third-Party MCP Sprawl: Adding 10 downstream MCP servers directly to your agent configuration dumps 50–100 tool definitions into every prompt header, diluting tool-calling accuracy and inflating baseline context costs.
- Confounded Causation & Hallucinatory Evolution: Agents mutate rules based on spurious correlation during complex multi-step sessions without isolating whether a rule actually helped, hurt, or was contested by confounding variables.
EvoKernel solves all five with a deterministic local compiler, worktree evolution engine & routing kernel:
<div align="center"> <img src="./assets/gatekeeper-shotcraft.svg" alt="EvoKernel 4-Stage Deterministic Gatekeeper" width="100%" /> </div>📊 Comprehensive Competitive Benchmark Matrix
| Dimension | MemGPT / Letta | Aider | Direct MCP Proxies | affaan-m/ECC | AMAP-ML/SkillClaw | 🧬 EvoKernel v0.3.0 (Ours) |
| :--- | :--- | :--- | :--- | :--- | :--- | :--- |
| Primary Focus | Stateful conversational agent DB | Git-centric terminal pair programmer | Pass-through MCP aggregation |
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
