Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mickeyyaya/evolve-loopnpx agentmods add skills/mickeyyaya/evolve-loop/publishWrote 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/publish)<a href="https://agentmods.dev/skills/mickeyyaya/evolve-loop/publish"><img src="https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/publish/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/publish"><img src="https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/publish.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.00059 | $0.02582 |
| Opus 5.5 | $0.00024 | $0.01033 |
| Sonnet 5.5 | $0.00012 | $0.00516 |
| Haiku 4.5 | $0.00006 | $0.00258 |
Grade A, and why
publish 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 14d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/evo:publish
Canonical release entry point. Owns the full publish lifecycle: pre-flight → bump → changelog → ship → propagate → rollback-on-failure. NOT a synonym for "git push" — see docs/guides/publishing-releases.md for vocabulary.
What this skill does
When the user types /evo:publish 18.5.0 (or similar), invoke the go-native release pipeline with the target version. The pipeline owns every step (implementation: go/internal/releasepipeline/, journal under .evolve/release-journal/):
| Step | Operation | Failure → action |
|---|---|---|
| 1 | Pre-flight gate (evolve release-preflight) |
exit non-zero; abort, no mutations |
| 2 | Auto-changelog | abort |
| 3 | Version bump (6 markers) | abort |
| 4 | Rebuild tracked binary go/evolve |
abort |
| 5 | Consistency check (evolve release-consistency) |
abort, files in working tree |
| 6 | Atomic ship (evolve ship --class release) |
abort, nothing pushed |
| 7 | Marketplace propagation poll (up to 5 min default) | auto-rollback unless --no-rollback |
| 8 | Release verify: the committed go/evolve is the disk binary and reports the target version |
auto-rollback unless --no-rollback |
The order is the order in go/internal/releasepipeline/release_run.go. The guide docs/guides/publishing-releases.md gives the details of each step.
Steps 1–8 are the
gh-free pipeline binary. It cannot see GitHub CI — it ends with aNOTE: GitHub CI is NOT verified by this pipelineadvisory. CI gating is this skill's job (next section); never treat a green pipeline as a green CI.
CI gating (this skill adds what the binary cannot)
evolve release is self-contained and headless-safe, so it does not verify GitHub CI. This skill wraps the pipeline with two gh-based checks. If gh is unavailable, report "cannot verify CI — confirm manually" and stop; never silently skip.
Before invoking the pipeline — base CI must be green (catches "releasing from an already-red main", the v20.1.0 trigger):
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.
- 14d ago Changed · +2 lines · -7 tokens per session 504a788e4c4c
- 16d ago Changed · -4 lines 94c48d07687a
- 24d ago Changed 6a9f41c0e699
- 1mo ago First seen · 127 lines · 66 tokens per session scan A b49f11c24bd3
publish is a skill published in the GitHub repository mickeyyaya/evolve-loop (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 59 tokens to every session and 2,582 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-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"…
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.
changelog
Add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.
sw-ship
Ships the current work unit. Verifies all gates passed, creates a PR with evidence-mapped body, updates workflow state to shipped.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).