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 product-on-purpose/agent-skills-toolkit --skill askit-releasegit clone --depth 1 https://github.com/product-on-purpose/agent-skills-toolkitWrote 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/product-on-purpose/agent-skills-toolkit/askit-release)<a href="https://agentmods.dev/skills/product-on-purpose/agent-skills-toolkit/askit-release"><img src="https://agentmods.dev/badge/skills/product-on-purpose/agent-skills-toolkit/askit-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/product-on-purpose/agent-skills-toolkit/askit-release"><img src="https://agentmods.dev/badge/skills/product-on-purpose/agent-skills-toolkit/askit-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.00066 | $0.00626 |
| Opus 5 | $0.00033 | $0.00313 |
| Sonnet 5 | $0.00013 | $0.00125 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
askit-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 9d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
askit-release
Purpose
Cut a conformant release. Four modes: version computes the plugin version by the deterministic rule (one plugin version = the max component bump since the last release, sec 7.4); changelog promotes the [Unreleased] section to a dated version (Keep a Changelog); notes curates a user-facing RELEASE-NOTES.md distinct from the changelog (sec 10.6); gate runs the release-readiness checks (ADR 0022) so docs and version are correct before tagging. Authoring depth is in references/release-workflow.md; the committed checklist is ../../docs/internal/RELEASE.md.
When to use
When the user asks to cut or tag a release, bump the version, update the CHANGELOG or RELEASE-NOTES, or check whether the plugin is ready to release.
version mode
- Determine each component's bump since the last release (MAJOR / MINOR / PATCH) from its version and HISTORY.
- The plugin version bump is the MAX of the component bumps (MAJOR beats MINOR beats PATCH, sec 7.4). Apply it to
library.json(the version source of truth) and syncpackage.json(U9 keeps them equal).
changelog mode
- Promote
[Unreleased]to a dated[X.Y.Z]section (Keep a Changelog) and leave a fresh empty[Unreleased].
notes mode
- Curate
RELEASE-NOTES.md: a user-facing, highlights-first entry for the version, distinct from the full CHANGELOG (sec 10.6 / Gold G5).
gate mode
- Run the release-readiness gate (ADR 0022 /
docs/internal/RELEASE.md): version consistency (U9), a dated CHANGELOG section, RELEASE-NOTES present, README status current, generated surfaces drift-free (INDEX and manifests, G4), the conformance gate green (node scripts/check.mjs), and the manual Codex round-trip recorded. Stop with an actionable message on any failure.
Scope
library.json is the version source of truth; package.json follows (U9). The release-readiness gate is built incrementally (ADR 0022): version + dash + CHANGELOG-section now, the full Advanced gate at Gold. Marketplace registration happens only at the first Gold tag (D8); release does not register before then.
What ships with it
2 files 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.
- 9d ago First seen · 33 lines · 66 tokens per session scan A bf4bd6ec2ebd
askit-release is a skill published in the GitHub repository product-on-purpose/agent-skills-toolkit (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 66 tokens to every session and 626 once invoked, about $0.0003 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-31.
Other skills, from other repositories
re0-release
Walk a pending change through this repo's shipping and releasing checklist end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.
release-notes
Generate audience-targeted release announcements. Specify the audience (customers, internal team, investors, social media) and optionally a version or scope. Use after shipping to announce what was built.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
comet-archive
A workflow for the fifth stage of Comet Classic: archiving a completed change, merging its specification updates, and finishing the branch. It uses Comet commands and a fixed layout for tracking the change.
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…