Borrowing it
Nothing to install: this file belongs to antopolskiy/kanban-md. 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/antopolskiy/kanban-md/main/.agents/skills/release-kanban-md/SKILL.mdgit clone --depth 1 https://github.com/antopolskiy/kanban-mdWrote 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/antopolskiy/kanban-md/release-kanban-md)<a href="https://agentmods.dev/skills/antopolskiy/kanban-md/release-kanban-md"><img src="https://agentmods.dev/badge/skills/antopolskiy/kanban-md/release-kanban-md/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/antopolskiy/kanban-md/release-kanban-md"><img src="https://agentmods.dev/badge/skills/antopolskiy/kanban-md/release-kanban-md.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.00071 | $0.01098 |
| Opus 5.5 | $0.00028 | $0.00439 |
| Sonnet 5.5 | $0.00014 | $0.00220 |
| Haiku 4.5 | $0.00007 | $0.00110 |
Grade A, and why
release-kanban-md 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 23d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release kanban-md
Carry an explicitly requested release from preflight through a verified GitHub release. A request to inspect, plan, or draft a release does not authorize pushing a tag or editing a live release; perform remote mutations only when the user has asked to release or publish.
Release invariants
- A version tag triggers the GitHub Actions
releaseworkflow, which uses GoReleaser to create the GitHub release and its artifacts. - Never run
gh workflow run release; tag push already triggers the workflow and a manual dispatch can create a duplicate build. - Never run
gh release create. Let GoReleaser create the release, then update its title and notes withgh release editafter CI succeeds. - Never move, delete, or reuse a tag that has been pushed. After a non-transient failure, fix the cause and choose a new, higher version.
- Decide the version autonomously using semver: patch for fixes, minor for backward-compatible features, and major for breaking changes. Do not ask the user to confirm the version.
- A release is complete only when the workflow is green, the generated release exists, its human-written notes are published, and the final release is verified.
1. Preflight
Work from a clean, up-to-date main containing exactly the changes intended for
release. Do not discard, overwrite, or silently stash unrelated user changes.
git branch --show-current
git status --short
git fetch origin --tags
git status --short --branch
git tag --sort=-version:refname | head -20
gh release list --limit 100
If main is dirty, diverged, or missing intended work, resolve that through the
normal project development workflow before releasing. Run the release-appropriate
verification, normally:
make precommit
Do not tag a revision that fails required tests or lint.
2. Inspect changes and choose the version
Identify the previous release tag and review the user-visible changes, including outside contributions that may need attribution:
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.
- 23d ago First seen · 138 lines · 71 tokens per session scan A d9d1d824a0e3
release-kanban-md is a skill published in the GitHub repository antopolskiy/kanban-md (226 stars, last pushed 23d ago), licensed MIT. It adds 71 tokens to every session and 1,098 once invoked, about $0.0003 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-10-06.
Other skills, from other repositories
gh-infra
Overview of gh-infra and command workflow (import, validate, plan, apply). Use when managing GitHub repository settings, labels, actions settings, rulesets, secrets, variables, or files declaratively via YAML manifests.
aiox-devops
Activate Gage (devops) for GitHub Repository Manager & DevOps Specialist. Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized to push to remote repository.
aiox-devops
GitHub Repository Manager & DevOps Specialist (Gage). Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized...
hatch3r-release
Cuts a release with version bump, changelog, tagging, and deploy verification. Use when preparing a release, cutting a version, or deploying to production.
ship-pr
Ship Skill: Creates PRs from feature branches, waits for CI, merges, and deploys using whatever mechanism the repo actually uses. MANDATORY TRIGGERS: ship, deploy, release, merge, create PR, push, go live, launch.
automating-devops
DevOps knowledge reference covering Git workflows, testing strategies, DevSecOps, release pipeline orchestration (release.yml, multi-arch images, cosign integration), CI/CD pipelines, database management, observability, and performance optimization. Use when working with Git, CI/CD, release pipelines, ghcr image…