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 mickeyyaya/evolve-loop --skill shipgit clone --depth 1 https://github.com/mickeyyaya/evolve-loopWrote 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/mickeyyaya/evolve-loop/ship)<a href="https://agentmods.dev/skills/mickeyyaya/evolve-loop/ship"><img src="https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/ship/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/mickeyyaya/evolve-loop/ship"><img src="https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/ship.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.00036 | $0.00732 |
| Opus 5.5 | $0.00014 | $0.00293 |
| Sonnet 5.5 | $0.00007 | $0.00146 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
ship 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ship
Sprint 3 composable skill. Wraps the Ship phase. The atomic commit at the end of every successful cycle.
When to invoke
- After
auditreturns Verdict PASS (or WARN with explicit override) - Cycle is in
auditphase, transitioning toship
When NOT to invoke
- Audit verdict is FAIL or ABORT
- The current tree-state SHA differs from what the auditor saw (cycle-binding violation)
- Ship class is unclear (use
--class cycle,--class manual, or--class releaseexplicitly)
Workflow
| Step | Action | Exit criteria |
|---|---|---|
| 1 | Verify audit verdict = PASS, or a WARN that the WARN rule of go/internal/phases/audit/audit_rules.go lets ship. evolve ship checks the audit binding itself (go/internal/phases/ship/audit.go) |
Binding check passes |
| 2 | Run evolve release-consistency <version> for consistency check |
Markers consistent |
| 3 | Run evolve ship --class cycle "<commit message>" |
Atomic commit created. Only the evolve release path makes a tag |
| 4 | Verify ledger entry added | kind: "ship" with cycle binding |
Single-writer invariant
Ship is ATOMIC by design — even if other phases fan out, Ship cannot. There is one git commit per cycle. The ship lock serializes concurrent ship attempts: evolve ship holds a flock on .evolve/ship.lock while it commits, merges and pushes (go/internal/phases/ship/gitops.go).
Cycle-binding (v8.13.0+)
evolve ship (go/internal/phases/ship/audit.go) refuses to ship if the current tree-state SHA differs from the SHA captured at audit time (in the auditor's ledger entry). Prevents "audit cycle 50, ship cycle 51" exploits. This guarantee is preserved through Sprint 3's tri-layer refactor.
Phase facts
| Fact | Value |
|---|---|
| Phase | ship (control archetype, mandatory) |
| Persona | agents/evolve-orchestrator.md |
| Profile | .evolve/profiles/orchestrator.json — CLI codex-tmux, tier balanced, single-writer |
| Inputs | audit-report.md |
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.
- 2d ago Changed 698cd3d8a39c
- 14d ago Changed · -1 lines · +10 tokens per session c3add7d04f0b
- 1mo ago First seen · 61 lines · 26 tokens per session scan A a4eaba432e03
ship is a skill published in the GitHub repository mickeyyaya/evolve-loop (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 36 tokens to every session and 732 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…
git-branchless
Use when asked for multi-commit stack edits, rebases, fixups, or stacked-PR publishing with branchless git idioms. Not for plain-git workflows in repos without branchless.
review
Structured code review with parallel audit agents, confidence-scored triage, and optional auto-fix. Examines uncommitted changes, staged diffs, commit ranges, or specific paths. Produces a tiered report (MUST-FIX / RECOMMENDED / NIT) backed by evidence, then optionally applies fixes with verification.
bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when npm run validate reports a version mismatch.
release-docs
Diff-driven documentation sync after a release. Determines what source files changed, delegates changelog to zuvo:docs, updates only docs whose source changed. Flags: --dry-run, explicit range argument.