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 khaosans/operator-etl --skill operator-releasegit clone --depth 1 https://github.com/khaosans/operator-etlWrote 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/khaosans/operator-etl/operator-release)<a href="https://agentmods.dev/skills/khaosans/operator-etl/operator-release"><img src="https://agentmods.dev/badge/skills/khaosans/operator-etl/operator-release/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/khaosans/operator-etl/operator-release"><img src="https://agentmods.dev/badge/skills/khaosans/operator-etl/operator-release.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.00042 | $0.00395 |
| Opus 5.5 | $0.00017 | $0.00158 |
| Sonnet 5.5 | $0.00008 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
operator-release 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 1mo 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.
What it actually says
Release — Operator ETL
Load: merge-feature-pr.md → cut-release.md · Humans: RELEASING.md · VERSIONING.md
Rules
- Run
./scripts/verify.shbefore claiming green. - Feature PRs:
[Unreleased]CHANGELOG only — never bumppyproject.tomlversion. - Do not merge while required CI is red or pending.
- Prefer squash-merge.
- Release = dedicated freeze PR → merge → annotated
v*tag push → watchrelease.yml. - Never retag / move a published tag.
- Software release ≠ FOIA publish (agents-never-publish-prod).
- Skip
make shareunless the user asked for external PDF share.
Agent workflow
verify → finish open feature PRs (Unreleased + CI) → merge
→ release branch (freeze CHANGELOG + bump versions)
→ verify → merge release PR
→ git tag -a vX.Y.Z && git push origin vX.Y.Z
→ confirm Release / GHCR / Packages
→ append okf/log.md
After a freeze
Update implementation-status.md if status changed; append okf/log.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.
- 1mo ago First seen · 38 lines · 42 tokens per session scan A 856fd5764176
operator-release is a skill published in the GitHub repository khaosans/operator-etl (0 stars, last pushed 7d ago), licensed Apache-2.0. It adds 42 tokens to every session and 395 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-04.
Other skills, from other repositories
datacoolie-release
Upload one locally verified DataCoolie environment artifact to the deployment path declared in datacoolie.yml. This skill never activates, executes, installs, deletes, or provisions a workload.
release-rollback
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of…
release-tag
Cut a release tag behind a real tier gate and cloud approval readback. The approval, task, approved commit, and resulting tag are bound; self-approval and HEAD drift fail closed. Prod prefixes remain refused.
git-ops
Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
releasing-prod
A controlled process for deploying already tested changes to the production environment. Production is the live environment used by users, and this process includes owner approval, database migration checks, deployment, and smoke tests.