evolve

A command that groups related learned working patterns, called instincts, into reusable skills, commands, or agents. It can examine all instincts or limit the review to a specific area such as testing.

In plain words
What is it for?
Use it to review possible groupings, preview proposed changes, or generate higher-level commands, skills, and agents from related instincts.
Why use it?
It helps turn scattered repeated patterns into clearer reusable building blocks.

Command

Install

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.

agentmods
npx agentmods add commands/oguzsh/claudey/evolve
Clone the repo
git clone --depth 1 https://github.com/oguzsh/claudey
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,199 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.01199
Opus 5 $0.00006 $0.00600
Sonnet 5 $0.00003 $0.00240
Haiku 4.5 $0.00001 $0.00120

Measured 2d ago against content hash 3121ed022025, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

evolve 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 2d 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.

Origin

This is a copy

91% identical to evolve — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

commands/evolve.md · 195 lines

How it starts

The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Evolve Command

Implementation

Run the instinct CLI using the plugin root path:

python3 "${CLAUDE_PLUGIN_ROOT}/skills/continuous-learning-v2/scripts/instinct-cli.py" evolve [--generate]

Or if CLAUDE_PLUGIN_ROOT is not set (manual installation):

python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py evolve [--generate]

Analyzes instincts and clusters related ones into higher-level structures:

  • Commands: When instincts describe user-invoked actions
  • Skills: When instincts describe auto-triggered behaviors
  • Agents: When instincts describe complex, multi-step processes

Usage

/evolve                    # Analyze all instincts and suggest evolutions
/evolve --domain testing   # Only evolve instincts in testing domain
/evolve --dry-run          # Show what would be created without creating
/evolve --threshold 5      # Require 5+ related instincts to cluster

Evolution Rules

→ Command (User-Invoked)

When instincts describe actions a user would explicitly request:

  • Multiple instincts about "when user asks to..."
  • Instincts with triggers like "when creating a new X"
  • Instincts that follow a repeatable sequence

Example:

  • new-table-step1: "when adding a database table, create migration"
  • new-table-step2: "when adding a database table, update schema"
  • new-table-step3: "when adding a database table, regenerate types"

→ Creates: new-table command

→ Skill (Auto-Triggered)

When instincts describe behaviors that should happen automatically:

  • Pattern-matching triggers
  • Error handling responses
  • Code style enforcement

Example:

  • prefer-functional: "when writing functions, prefer functional style"
  • use-immutable: "when modifying state, use immutable patterns"
  • avoid-classes: "when designing modules, avoid class-based design"

→ Creates: functional-patterns skill

→ Agent (Needs Depth/Isolation)

When instincts describe complex, multi-step processes that benefit from isolation:

  • Debugging workflows
  • Refactoring sequences
  • Research tasks

Read the full file on GitHub · 195 lines

Changes

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.

  1. 2d ago First seen · 195 lines · 13 tokens per session scan A 3121ed022025

Subscribe to this mod's changes

evolve is a command published in the GitHub repository oguzsh/claudey (5 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 1,199 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to evolve, differing in 16 lines, and is treated as a copy.