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/adechassey/coclaude/releasenpx skills add adechassey/coclaude --skill releasegit clone --depth 1 https://github.com/adechassey/coclaudeWrote 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/adechassey/coclaude/release)<a href="https://agentmods.dev/skills/adechassey/coclaude/release"><img src="https://agentmods.dev/badge/skills/adechassey/coclaude/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.1 | $0.00046 | $0.01392 |
| Opus 5 | $0.00023 | $0.00696 |
| Sonnet 5 | $0.00009 | $0.00278 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade A, and why
release scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(git *) Bash(gh *) Bash(jq *) Bash(cat *) Bash(grep *) Bash(ls *) Bash(curl *) Bash(node *) Read Edit Write How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Current state
# Each line ends with `|| true` so a missing optional file (Cargo.toml,
# pyproject.toml, etc.) doesn't fail the whole block — ls's exit code 2
# propagates through `&&` even when stderr is silenced.
echo "=== branch ===" && git rev-parse --abbrev-ref HEAD 2>/dev/null || true
echo "=== clean? ===" && git status --short
echo "=== upstream sync ===" && git status -sb | head -1
echo "=== last tags ===" && git tag --sort=-version:refname | head -5
echo "=== remote ===" && git remote get-url origin 2>/dev/null || true
echo "=== release workflows ===" && ls .github/workflows/ 2>/dev/null || true
echo "=== node version files ===" && ls package.json src/version.ts version.ts lib/version.ts 2>/dev/null || true
echo "=== rust version files ===" && ls Cargo.toml 2>/dev/null || true
echo "=== python version files ===" && ls pyproject.toml 2>/dev/null || true
What you're doing
The user wants to cut a release. Argument $1 is one of:
patch/minor/major— semver bump from the current version- explicit version like
1.2.3orv1.2.3 - empty — ask the user which they want
Workflow
-
Preflight — stop or ask the user if any of these are off:
- Working tree dirty (offer to commit/stash first, or abort)
- On a non-default branch (warn and confirm; some projects do release branches)
- Local branch behind origin (pull or warn)
- Tag for the target version already exists (always abort — don't retag)
- npm name collision (Node projects only): if a
package.jsonexists and isn't marked"private": true, query the npm registry —curl -fsS -o /dev/null -w '%{http_code}' https://registry.npmjs.org/<name>/<NEW>. A200means that version is already published and any CInpm publishwill fail later. Abort early; ask the user to bump further. A404means it's free to publish.
-
Discover version-bearing files. Be thorough; many projects have more than one:
package.json(top-levelversion)src/version.ts/src/version.js/version.ts/version.js/lib/version.*(look for aVERSION = "..."literal)Cargo.toml([package].version)pyproject.toml([project].versionor[tool.poetry].version)__init__.pyfiles with__version__ = "..."
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 86 lines · 46 tokens per session scan A 2e1c66e17e70
release is a skill published in the GitHub repository adechassey/coclaude (2 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 1,392 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
push-release
Push to GitHub and optionally bump version to trigger PyPI release.
omh-deploy-and-monitor
This is a Hermes-native deploy-and-monitor workflow skill.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
release
Cut a new SlackCLI release end to end — survey commits since the last tag, recommend a SemVer bump, open the release issue, prepare the version bump and CHANGELOG promotion on a branch, open the linked PR, and after merge push the annotated tag that publishes binaries and updates the Homebrew tap. Use when asked to…
release-notes
Draft user-facing release notes from a git log range. Trigger when the user asks for "release notes", "changelog entry", or "what shipped this week" with a git ref range. Output is markdown sections grouped by Features / Fixes / Breaking with PR links.