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 agentmods add skills/junghwayang/oh-my-codex/releasenpx skills add junghwaYang/oh-my-codex --skill releasegit clone --depth 1 https://github.com/junghwaYang/oh-my-codexWrote 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/junghwayang/oh-my-codex/release)<a href="https://agentmods.dev/skills/junghwayang/oh-my-codex/release"><img src="https://agentmods.dev/badge/skills/junghwayang/oh-my-codex/release.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00517 |
| Opus 5 | $0.00000 | $0.00259 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00052 |
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 3d 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 Skill
Version management and release preparation.
When to Use
- Preparing releases
- Version bumping
- Changelog generation
- Release notes
- Tag management
Release Process
1. Pre-Release Checks
□ All tests passing
□ No critical bugs
□ Documentation updated
□ Breaking changes documented
□ Dependencies up to date
2. Version Bump
Semantic Versioning: MAJOR.MINOR.PATCH
MAJOR - Breaking changes
MINOR - New features (backward compatible)
PATCH - Bug fixes (backward compatible)
3. Changelog Generation
## [1.2.0] - 2026-02-13
### Added
- New feature X (#123)
- Support for Y
### Changed
- Improved performance of Z
### Fixed
- Bug in authentication (#456)
### Deprecated
- Old API endpoint (use /v2 instead)
### Removed
- Legacy support for X
### Security
- Updated dependencies
4. Release Notes
# Release 1.2.0
## Highlights
- 🚀 Major performance improvements
- ✨ New dashboard features
- 🔒 Security updates
## Breaking Changes
None in this release.
## Migration Guide
No migration needed.
## Contributors
- @user1
- @user2
Commit Convention
feat: new feature
fix: bug fix
docs: documentation
style: formatting
refactor: code restructure
perf: performance
test: testing
chore: maintenance
Usage
release: prepare version 1.2.0
release: generate changelog from commits
release: create release notes for v2.0.0
Automation
# Bump version
npm version minor
# Generate changelog
npx conventional-changelog -p angular -i CHANGELOG.md -s
# Create tag
git tag -a v1.2.0 -m "Release 1.2.0"
# Push with tags
git push origin main --tags
Best Practices
- Release often - Small, frequent releases
- Automate - CI/CD for releases
- Document - Clear changelogs
- Communicate - Notify users of changes
- Rollback plan - Know how to revert
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.
- 3d ago First seen · 122 lines · 0 tokens per session scan A b232235d1085
release is a skill published in the GitHub repository junghwaYang/oh-my-codex (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 517 tokens. 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
publish-registry
Publish @agentos-software/ registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.