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.
npx skills add cmdr-chara/codex-toolkit --skill codebase-evolution-controllergit clone --depth 1 https://github.com/cmdr-chara/codex-toolkitWrote 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/skills/cmdr-chara/codex-toolkit/codebase-evolution-controller)<a href="https://agentmods.dev/skills/cmdr-chara/codex-toolkit/codebase-evolution-controller"><img src="https://agentmods.dev/badge/skills/cmdr-chara/codex-toolkit/codebase-evolution-controller/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/skills/cmdr-chara/codex-toolkit/codebase-evolution-controller"><img src="https://agentmods.dev/badge/skills/cmdr-chara/codex-toolkit/codebase-evolution-controller.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.00039 | $0.00691 |
| Opus 5.5 | $0.00016 | $0.00276 |
| Sonnet 5.5 | $0.00008 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
codebase-evolution-controller 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 24d 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Evolution Controller
Move a repository from a known current state to a defined target without breaking consumers or losing rollback.
Trigger boundary
Use this skill for dependency/runtime upgrades, framework migrations, schema or API transitions, compatibility windows, staged rollout, and retirement of legacy paths.
Do not trigger for an unexplained failure, ordinary feature work, measured performance tuning, security-only review, or final release approval.
Required inputs
Resolve current and target states, repository/working-tree identity, manifests/lockfiles, consumers, compatibility constraints, data/schema impact, rollout environment, rollback path, and authorization.
For a read-only manifest inventory, run:
python skills/codebase-evolution-controller/scripts/manifest_inventory.py . --format markdown
Verify the resulting signals against authoritative repository evidence.
Safety baseline
- Preserve uncommitted user work.
- Do not silently upgrade, regenerate, rewrite lockfiles, or remove compatibility paths during discovery.
- Verify volatile target-version, support, security, and compatibility claims from current primary sources.
- Keep irreversible data/schema changes behind explicit recovery evidence.
Workflow
- Define the transition contract. Record current state, target state, consumers, non-negotiable behavior, compatibility window, rollout, rollback, and removal criteria.
- Capture a baseline. Establish build/test/runtime evidence and the existing contract before edits.
- Map compatibility. Use
references/compatibility-evidence.md; identify producer/consumer order, mixed-version periods, generated clients, persisted data, and operational dependencies. - Check dependency risk when relevant. Read
references/dependency-risk.mdfor CVE reachability, maintenance, supply-chain, lockfile, and license considerations. - Check database migration safety when relevant. Read
references/database-migration-safety.mdbefore production DDL/backfills or expand-contract work. - Build stages. Use
references/migration-plan-template.md. Each stage must be independently verifiable and have an exit/rollback condition. - Implement bounded stages. Preserve compatibility until all required consumers have moved; do not delete the old path early.
- Verify and roll out. Test old/new and mixed states where relevant, observe rollout signals, and confirm rollback/forward-recovery.
- Contract. Remove legacy paths only after their retirement criteria are proven.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 24d ago Changed · -157 lines · -42 tokens per session fc8a01e6cb86
- 1mo ago First seen · 215 lines · 81 tokens per session scan A d18fa62d1a7a
codebase-evolution-controller is a skill published in the GitHub repository cmdr-chara/codex-toolkit (2 stars, last pushed 11d ago), licensed MIT. It adds 39 tokens to every session and 691 once invoked, about $0.0002 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.
Other skills, from other repositories
trace
Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find the root cause", "why…
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
skeptical-triage
Reusable 3-round self-challenge + arbiter pattern for filtering false positives from findings/verdicts. Use when the cost of a false-positive gate block exceeds the cost of 4 extra LLM turns.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
code-coherence-review
Reviews code and plans for logic coherence, correctness, and structural integrity.