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 Andamio-Platform/coach --skill releasegit clone --depth 1 https://github.com/Andamio-Platform/coachWrote 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/andamio-platform/coach/release)<a href="https://agentmods.dev/skills/andamio-platform/coach/release"><img src="https://agentmods.dev/badge/skills/andamio-platform/coach/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/andamio-platform/coach/release"><img src="https://agentmods.dev/badge/skills/andamio-platform/coach/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.00024 | $0.01037 |
| Opus 5.5 | $0.00010 | $0.00415 |
| Sonnet 5.5 | $0.00005 | $0.00207 |
| Haiku 4.5 | $0.00002 | $0.00104 |
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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Release
Publish a new version of Coach to all distribution channels.
Instructions
1. Preflight Checks
Before starting, verify the release is ready:
- Confirm you are on the
mainbranch:git branch --show-current - Confirm the working tree is clean:
git status - If there are uncommitted changes, stop and ask the user to commit or stash first.
2. Determine Version Bump
Ask the user which version bump to apply:
What type of release is this?
1. Patch (x.x.1) — Wording improvements, typo fixes, minor knowledge corrections
2. Minor (x.1.0) — New skills, significant instruction rewrites, new knowledge seed patterns
3. Major (1.0.0) — Knowledge schema changes that break compound data, or skill removals
Read the current version from package.json (the version field) and compute the new version.
3. Generate Changelog Entry
Review what changed since the last release:
git log $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~10)..HEAD --oneline
If no tags exist yet, review all recent commits.
Draft a changelog entry in Keep a Changelog format. Group changes under the appropriate headings:
- Added — new skills, new features
- Changed — modifications to existing skills or knowledge
- Fixed — bug fixes, corrections
- Removed — removed skills or features
Present the draft to the user for approval before writing.
4. Apply Version Bump
After the user approves the changelog, update versions in all locations:
4a. package.json
Run npm version <patch|minor|major> --no-git-tag-version to bump the version without creating a git tag (we tag manually later).
4b. .claude-plugin/plugin.json
Update the "version" field to match the new version.
4c. SKILL.md frontmatter
For each skill that changed in this release, update metadata.version in its SKILL.md frontmatter to the new version. Skills that did not change keep their existing version.
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 · 156 lines · 24 tokens per session scan A 264751db06e6
release is a skill published in the GitHub repository Andamio-Platform/coach (6 stars, last pushed 12d ago), licensed MIT. It adds 24 tokens to every session and 1,037 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
agentsop-llm-artifact-versioning
Enhancement overlay — version the WHOLE deployable LLM-app artifact as one bundle: prompts + compiled programs + model snapshot pins + retrieval config + eval-set version, versioned together so a deploy is reproducible and rollback is atomic. Activate when preparing to deploy an LLM app, when asking "what exactly is…
github-repo-management
Clone, create, fork repos; manage remotes, releases.
hyalo-changelog
Maintain Keep a Changelog files with Hyalo's changelog profile and add/release commands.
release-doi
A release procedure for research repositories that publish versions with a DOI, a permanent identifier for scholarly work, through Zenodo.
akiship
Full release ritual end-to-end — front-loaded checks, then an unattended pass. ACTIVATION = the literal token /akiship, or an imperative turn, in any language, ordering the release ritual for this repo. A question about it, or a completion word with no release object, activates nothing — consult the checklist and…
deploy-pipeline-runbook
Use when a release spans multiple systems or vendors, order of operations matters with rollback planned up front, or a failed step in one system could corrupt state in a downstream system.