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/alireza29675/teamctl/releasenpx skills add Alireza29675/teamctl --skill releasegit clone --depth 1 https://github.com/Alireza29675/teamctlWrote 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/alireza29675/teamctl/release)<a href="https://agentmods.dev/skills/alireza29675/teamctl/release"><img src="https://agentmods.dev/badge/skills/alireza29675/teamctl/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.00089 | $0.03489 |
| Opus 5 | $0.00044 | $0.01744 |
| Sonnet 5 | $0.00018 | $0.00698 |
| Haiku 4.5 | $0.00009 | $0.00349 |
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 4d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release body
This skill is the writing surface for cutting a release. It produces the public-facing GitHub release body: short, curated, scannable. The thing your users see on github.com/<org>/<repo>/releases and (if you've wired it) what an update command prints after upgrade.
This skill stops at a ratified body. The technical cascade (version bumps, CHANGELOG dating, tag push, cargo-dist or equivalent, smoke tests) is engineering's job; the placeholders are demarcated below.
Flow
Six beats, in order.
- Read the merge surface.
git log --oneline <last-tag>..origin/mainandgh pr list --state merged --search "merged:>=<date>"to gather the PRs that landed. ReadCHANGELOG.md[Unreleased]if engineering keeps one; that's the exhaustive surface, you'll write the curated short version. - Sort into tiers. Tier 1: the changes that genuinely change what a user can DO (verbs, not nouns). Tier 2: the quiet wins. Cut: engineering-only changes (test deflakes, build hygiene, internal refactors). Hold: known-broken features; never lead the public with a foot-gun.
- Pick the shape. Count weighty Tier-1 features. Three means triplet shape. Zero to two means bullets shape. A single fix means hotfix shape. See Shape variants below. The shape determines headline and body structure.
- Read the last shipped body side-by-side. Match its rhythm: word count per paragraph, sentence count, bullet density. Drift on rhythm is the most common reason a body comes back "not nice" despite hitting the right structure.
- Surface to ratify. Pass the draft to whoever ratifies user-facing copy (owner, lead, you-yesterday). Include named variant questions so the ratify is one-round.
- Hand off the technical cascade. Once ratified, pass the approved body to engineering to wire into
gh release create. The placeholder checklist below is theirs to execute.
Voice rails
The release body is the most-screenshotted artifact of any version cut. It lives on github.com long after you've forgotten it. Get it right.
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.
- 4d ago First seen · 189 lines · 89 tokens per session scan A ea02c3001497
release is a skill published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 3,489 once invoked, about $0.0004 per session on Opus 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-30.
Other skills, from other repositories
release
Cut a versioned release of the DOS kernel — bump the version, draft release notes, commit, tag, push to master, and create a GitHub release. The tag push triggers the gated PyPI publish pipeline (publish.yml); the skill surfaces the run and its approval gate.
stable-release
Promote an already-shipped rolling release (vX.Y.Z) of the DOS kernel to a named stable channel — gated on a green kernel suite + a green third-party CI run on the candidate + a clean truth syscall + a soak window. Writes an evidence file and adds a stable/ git tag on the same commit. Does NOT bump versions or build…
finishing-a-development-branch
Presents merge, PR, or cleanup options once tests pass.
merging-to-main
Keyword-gated by name. Merges a ready branch to main: PR, CI, cleanup.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…