A command that starts an analysis of an agent ecosystem and its possible improvements.

Use it when you want the system to review itself and identify or apply ecosystem changes.

It provides a way to examine the ecosystem and trigger its evolution process.

How fltman/claude-code-hive configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to fltman/claude-code-hive. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/fltman/claude-code-hive/main/.claude/commands/evolve.md

Clone the repo

git clone --depth 1 https://github.com/fltman/claude-code-hive

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/fltman/claude-code-hive/evolve/github.svg)](https://agentmods.dev/commands/fltman/claude-code-hive/evolve)

Your own site

<a href="https://agentmods.dev/commands/fltman/claude-code-hive/evolve"><img src="https://agentmods.dev/badge/commands/fltman/claude-code-hive/evolve/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/fltman/claude-code-hive/evolve"><img src="https://agentmods.dev/badge/commands/fltman/claude-code-hive/evolve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 832 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00009	$0.00832
Opus 5.5	$0.00004	$0.00333
Sonnet 5.5	$0.00002	$0.00166
Haiku 4.5	$0.00001	$0.00083

Measured 2mo ago against content hash c6901edafaa2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

.claude/commands/evolve.md · 157 lines

How it starts

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

EVOLVE - Ecosystem Evolution

Trigger a deep analysis of the capability ecosystem. HIVE observes patterns, detects inefficiencies, and proposes evolutionary changes.

Process

1. Full Ecosystem Scan

Invoke HIVE for deep analysis:

Use HIVE to perform evolution analysis.

HIVE should:
1. Read all active capabilities in .claude/capabilities/
2. Analyze energy levels
3. Detect overlaps between capabilities
4. Identify gaps in coverage
5. Review dissolved capabilities for resurrection potential
6. Propose evolutionary operations

2. Analysis Dimensions

Energy Analysis

Which capabilities are overloaded (>90)?
Which are fading (<20)?
Which are stable?

Overlap Analysis

Are multiple capabilities handling similar domains?
Could they merge for efficiency?

Gap Analysis

What requests have no capability to handle them?
What domains are underserved?

Pattern Analysis

Which capabilities are frequently invoked together?
Are there implicit dependencies?

Void Analysis

Are there dissolved capabilities relevant to current needs?
Should any be resurrected?

3. Evolution Proposals

HIVE presents findings:

EVOLUTION ANALYSIS
═══════════════════════════════════════════════════════════════

OBSERVATIONS
───────────────────────────────────────────────────────────────
1. react-rendering and ui-components have 60% overlap
2. api-integration energy at 92 (overloaded)
3. No capability handles authentication
4. postgres-ops unused for 3 sessions

PROPOSALS
───────────────────────────────────────────────────────────────

[A] MERGE: react-rendering + ui-components → frontend-core
    Rationale: High overlap, often invoked together
    Energy inheritance: max(80, 65) = 80
    
[B] SPLIT: api-integration → rest-api + graphql-api  
    Rationale: Overloaded, natural division line
    Energy inheritance: 46 each
    
[C] SPAWN: auth-flow
    Rationale: Gap detected - auth requests unhandled
    Suggested energy: 50
    
[D] DISSOLVE: postgres-ops
    Rationale: Energy 12, unused 3 sessions
    Alternative: MUTATE to broader data-ops?

───────────────────────────────────────────────────────────────
Select operations to execute (comma-separated) or 'none':
>

Read the full file on GitHub · 157 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.

2mo ago First seen · 157 lines · 9 tokens per session scan A c6901edafaa2

Subscribe to this mod's changes

evolve is a command published in the GitHub repository fltman/claude-code-hive (6 stars, last pushed 10d ago), licensed MIT. It adds 9 tokens to every session and 832 once invoked, about $0.0000 per session on Opus 5.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-31.

Building agents

evolve next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
evolvefltman/claude-code-hive	Command	6	10d ago	MIT	A	9	Claude Code
checklistgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
convergegithub/spec-kit	Command	148k	today	MIT	A	35	Claude Code
speckit.bug.testgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	today	MIT	A	26	Claude Code

claude-code-hive: Command for Claude Code