Borrowing it
Nothing to install: this file belongs to snoozelieb/coach-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/snoozelieb/coach-mcp/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/snoozelieb/coach-mcpWrote 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/snoozelieb/coach-mcp/release)<a href="https://agentmods.dev/skills/snoozelieb/coach-mcp/release"><img src="https://agentmods.dev/badge/skills/snoozelieb/coach-mcp/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/snoozelieb/coach-mcp/release"><img src="https://agentmods.dev/badge/skills/snoozelieb/coach-mcp/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.00062 | $0.00942 |
| Opus 5.5 | $0.00025 | $0.00377 |
| Sonnet 5.5 | $0.00012 | $0.00188 |
| Haiku 4.5 | $0.00006 | $0.00094 |
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 yesterday.
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.
`curl "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.snoozelieb/coach-mcp"` How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releasing garmin-coach-mcp
Full runbook: docs/PUBLISHING.md. This skill is the operational checklist with
the machine-specific facts that are NOT in the runbook.
Preflight
git branch --show-currentmust bemain, tree clean, up to date with origin.- Full suite green locally:
python -m pytest -q. CHANGELOG.md[Unreleased]section describes what ships.
1. Version triple-bump (test-enforced)
Bump ALL THREE, or tests/test_packaging.py fails:
pyproject.toml→versionserver.json→ bothversionfields (top level ANDpackages[0])CHANGELOG.md→ retitle[Unreleased]to## [x.y.z] - YYYY-MM-DD
Run python -m pytest tests/test_packaging.py -q to confirm, then commit.
2. Push + tag — the auth dance (IMPORTANT)
The machine has two GitHub accounts (snoozelieb owns this repo; the default
gh account is a work account that cannot push here or create releases). The
repo has a local credential.helper = !gh auth git-credential. The user does
NOT want browser auth flows (password manager). Run these via the Bash tool,
NOT PowerShell, and never compound the commands:
gh auth switch --user snoozelieb
git push origin main
git tag vX.Y.Z
git push origin vX.Y.Z
gh auth switch # ALWAYS switch back afterwards (no --user needed: toggles to the other account)
The tag push triggers .github/workflows/release.yml: builds sdist+wheel
(verifies tag matches pyproject.toml), publishes to PyPI via trusted
publishing (OIDC, no tokens), creates the GitHub Release with the CHANGELOG
excerpt, and registers server.json with the MCP Registry (job
publish-to-mcp-registry, OIDC — no token). Note: the local gh default is
the work account, which cannot create releases on this repo — that's why
CI does it.
3. Verify
- Actions → Release run is green.
- https://pypi.org/project/garmin-coach-mcp/ shows the new version.
- GitHub Release exists with wheel + sdist.
- The registry lists the version (the job retries up to 5 min while PyPI lags):
curl "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.snoozelieb/coach-mcp"
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.
- yesterday Changed · +13 lines · -1 tokens per session a8cafa7703ea
- 1mo ago First seen · 74 lines · 63 tokens per session scan A b6e23be83de3
release is a skill published in the GitHub repository snoozelieb/coach-mcp (3 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 942 once invoked, about $0.0002 per session on Opus 5.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
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
Fully automate a release with version-bump and childhood.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.