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 PromptPartner/agentsmith --skill release-checkgit clone --depth 1 https://github.com/PromptPartner/agentsmithWrote 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/promptpartner/agentsmith/release-check)<a href="https://agentmods.dev/skills/promptpartner/agentsmith/release-check"><img src="https://agentmods.dev/badge/skills/promptpartner/agentsmith/release-check/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/promptpartner/agentsmith/release-check"><img src="https://agentmods.dev/badge/skills/promptpartner/agentsmith/release-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.00558 |
| Opus 5.5 | $0.00017 | $0.00223 |
| Sonnet 5.5 | $0.00009 | $0.00112 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
release-check 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Check — Orchard
Cutting a release for Orchard is mechanical but easy to half-do (tag without the migration check, bump the version but forget the changelog). This skill is the checklist so nothing slips. It loads only when you're releasing — everyday work doesn't pay for it.
When this fires
You type /release-check, or you're about to tag a new Orchard version.
Checklist
Walk these in order. Stop at the first failure, fix it, restart — a release is atomic.
- Clean tree, right branch.
git statusis clean and you're onmain(or the release branch). No uncommitted work rides along in a tag. - Bump the version. Update
versioninpyproject.toml. Use semver: breaking API/contract change → major; new endpoint/field → minor; fix only → patch. - Migrations present and current.
alembic checkis clean (no model-vs-history drift), and every new revision has been applied once against a dump of representative data, not just an empty DB.alembic checkproves agreement, not applicability — this step proves applicability. - Verify is green. Run
scripts/verify.shand read the output:format,lint,types,migrations,testall pass. Within-a-layer green only — also confirm one real request path (TestClient against the full app) still works end to end. - Changelog updated. Add a dated section to
CHANGELOG.mdfor this version: what changed, and call out any API-contract or migration change explicitly so callers know to look. - Commit, then tag.
chore(release): vX.Y.Zcommit, thengit tag vX.Y.Z. Tag points at the release commit — never an earlier one. - Push commit and tag.
git push && git push --tags. Open/reference the GitHub release.
Notes
- If
alembic checkfails, you have a model change with no migration — that's a code bug, not a release step. Go back and add the revision before tagging. - Don't allowlist a secret to make a hook pass; the no-secrets rule is absolute (core).
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 · 41 lines · 43 tokens per session scan A 918facc4f6fe
release-check is a skill published in the GitHub repository PromptPartner/agentsmith (178 stars, last pushed 7d ago), licensed MIT. It adds 43 tokens to every session and 558 once invoked, about $0.0002 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-30.
Other skills, from other repositories
shared-tooling-changesets
Versioning and changelog management with @changesets/cli — adding changesets, version bumping, changelog generation, monorepo publishing, pre-release modes, and CI automation.
release-rollback
Plan and execute authorized release promotion or rollback with exact artifact and data compatibility. Use when deploying versions, changing traffic or recovering a bad release; do not equate reversing code with restoring data.
shared-tooling-git-hooks
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.
release-guard
Block releases that fail the licence and changelog policy, and bundle the team's release tooling into one installable package.
render-release-notes
Render release notes to HTML and check the rendered output in a browser.
merge
The ship gate — the only skill that pushes a feature branch, opens its PR and merges. --staging checks that pre-merge passed on the branch tip, pushes, opens the feature→staging PR, waits for green CI, merges, deploys, verifies, emits a human test script and stamps the staging sign-off on approval. --production ships…