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 RobinNorberg/oh-my-copilot --skill releasegit clone --depth 1 https://github.com/RobinNorberg/oh-my-copilotWrote 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/robinnorberg/oh-my-copilot/release)<a href="https://agentmods.dev/skills/robinnorberg/oh-my-copilot/release"><img src="https://agentmods.dev/badge/skills/robinnorberg/oh-my-copilot/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/robinnorberg/oh-my-copilot/release"><img src="https://agentmods.dev/badge/skills/robinnorberg/oh-my-copilot/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.00027 | $0.01946 |
| Opus 5.5 | $0.00011 | $0.00778 |
| Sonnet 5.5 | $0.00005 | $0.00389 |
| Haiku 4.5 | $0.00003 | $0.00195 |
Grade A, and why
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.
This is a copy
88% identical to release — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill
A thin, repo-aware release assistant. On first run it inspects the project and CI to derive release rules, stores them in .omg/RELEASE_RULE.md for future use, then walks you through a release using those rules.
Usage
/oh-my-copilot:release [version]
versionis optional. If omitted the skill will ask. Acceptspatch,minor,major, or an explicit semver like2.4.0.- Add
--refreshto force re-analysis of the repo even when a cached rule file exists.
Execution Flow
Step 0 — Load or Build Release Rules
Check whether .omg/RELEASE_RULE.md exists.
If it does NOT exist (or --refresh was passed): Run the full repo analysis below and write the file.
If it DOES exist: Read the file. Then do a quick delta check — scan .github/workflows/ (or equivalent CI dirs: .circleci/, .travis.yml, Jenkinsfile, bitbucket-pipelines.yml, gitlab-ci.yml) for any modifications newer than the last-analyzed timestamp in the rule file. If relevant workflow files changed, re-run the analysis for those sections and update the file. Report what changed.
Step 1 — Repo Analysis (first run or --refresh)
Inspect the repo and answer the following. Write answers into .omg/RELEASE_RULE.md.
1a. Version Sources
- Locate all files that contain a version string matching the current version in
package.json/pyproject.toml/Cargo.toml/build.gradle/VERSIONfile / etc. - List each file and the field or regex pattern used to find the version.
- Detect whether there is a release automation script (e.g.
scripts/release.*,Makefile releasetarget,bump2version,release-it,semantic-release,changesets,goreleaser).
1b. Registry / Distribution
- npm (
package.jsonwithpublishConfigornpm publishin CI), PyPI (pyproject.toml+twine/flit), Cargo (Cargo.toml), Docker (Dockerfile+ push step), GitHub Packages, other. - Is there a CI step that publishes automatically on tag push? Which workflow file and job?
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 · 199 lines · 27 tokens per session scan A 4ad1bad93b5e
release is a skill published in the GitHub repository RobinNorberg/oh-my-copilot (5 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 1,946 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to release, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
release
Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASERULE.md, then guides the release.
skill-ship
Package and finalize completed work for delivery — use when a feature is done and ready to ship.
release
Release a new version of the DevoxxGenie IntelliJ plugin — prompt for the target version, bump it in the build files, write a curated CHANGELOG.md entry and plugin.xml change-notes from the git/PR history since the last tag, build to verify, then commit, tag, and publish a matching GitHub release. Use this whenever…
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
release-debrief
Summarises the delta between a tool's latest release and the last summary the user saw. Use when the user asks about what's new, the latest release, release notes, or the changelog of one of the supported tools: Claude Code, OpenCode, llama-swap, or llama.cpp.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.