evolve

A command that turns reviewed, reusable project knowledge into a shareable command or skill and proposes it for contribution through a human-reviewed pull request, a code change submitted for review.

In plain words
What is it for?
Use it to package vetted knowledge from the project profile into a reusable capability and prepare an upstream contribution.
Why use it?
It helps preserve useful lessons without promoting unreviewed or project-specific information automatically.

Command for Claude Code

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/zts0hg/codexspec/evolve
Clone the repo
git clone --depth 1 https://github.com/Zts0hg/codexspec

Made for: Claude Code.

Per session 19 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,047 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.01047
Opus 5 $0.00010 $0.00524
Sonnet 5 $0.00004 $0.00209
Haiku 4.5 $0.00002 $0.00105

Measured 2d ago against content hash 2621290195cb, 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.

.claude/commands/codexspec/evolve.md · 77 lines

How it starts

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

Evolve

Language Preference

Read .codexspec/config.yml. Two independent language controls apply (each falls back to language.output, then English):

  • Interaction language (language.interaction): language for all conversation with the user — questions, explanations, status messages, and codexspec CLI terminal output.
  • Document language (language.document): language for generated artifact files.

Converse in the interaction language. The compiled command/skill draft is a distributed template and MUST be authored in English (project i18n convention), regardless of language.document. PR title/body follow language.commit.

User Input

$ARGUMENTS

Operating Model

evolve turns vetted sediment in .codexspec/profile/ into a reusable capability and contributes it back to CodexSpec through a human-reviewed PR. It never merges unattended and never edits install artifacts.

Selecting what to promote

Promote only records that are both:

  1. status: vetted (never candidate or conflict), and
  2. general enough for the toolkit — the generality extension of distill's boundary test: "Is this useful to every CodexSpec user, or only to this project?"

Project-specific knowledge stays in the profile. Only generally-useful capability is promoted upstream. When nothing qualifies, stop and report — do not force a promotion.

This selection spans all six profile categories. strategies/ (metacognitive trigger → action rules) and runbooks/ (ordered multi-step procedures) are often the most promotable material — a vetted, general strategy or runbook compiles cleanly into a reusable skill/command — but they clear the same vetted gate as every other category; the gate is unchanged.

Compiling the draft

Compile the selected sediment into a SKILL.md / command-template draft that conforms to both:

  • Anthropic Agent Skills (SKILL.md + progressive disclosure), and
  • existing CodexSpec command-template conventions (YAML frontmatter + sections + ## Language Preference, English).

Read the full file on GitHub · 77 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 · 77 lines · 19 tokens per session scan A 2621290195cb

Subscribe to this mod's changes

evolve is a command published in the GitHub repository Zts0hg/codexspec (5 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 1,047 once invoked, about $0.0001 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-31.