Borrowing it
Nothing to install: this file belongs to aotter/mantle. 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/aotter/mantle/develop/.agent/skills/mantle-release/SKILL.mdgit clone --depth 1 https://github.com/aotter/mantleWrote 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/aotter/mantle/mantle-release)<a href="https://agentmods.dev/skills/aotter/mantle/mantle-release"><img src="https://agentmods.dev/badge/skills/aotter/mantle/mantle-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.1 | $0.00000 | $0.00895 |
| Opus 5 | $0.00000 | $0.00447 |
| Sonnet 5 | $0.00000 | $0.00179 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
mantle-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 3d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mantle Release Skill
Use this skill for a Mantle version bump, npm publish, Core or Starter tag, release recovery, or an explicit Landing release caused by Core.
Required reading
Before changing a version or running the controller, read completely:
docs/release-process.md.github/release.yml- root and workspace
package.jsonfiles - all four agent plugin manifests
.agents/plugins/marketplace.json.github/workflows/release.yml
Inspect the exact mantle-starters and mantle-landing commits pinned by the
controller. Inspect Landing deployment configuration only when
deploy_landing=true is explicitly in scope.
When changing release automation, follow docs/release-process.md section
"Changing release automation" before editing workflow code.
Contract
Public versions and tags are immutable. .github/workflows/release.yml is the
only release controller. Do not push a release tag, invoke the Starter worker,
or repair public state manually.
For the current pre-v0.1 alpha cadence:
- merge a reviewed release PR into
develop; - dispatch the controller from that merge commit;
- leave
deploy_landing=falseunless Landing was separately reviewed.
The controller gates source and exact-packed Starter before tagging Core,
publishes and verifies the registries, waits for the Starter's exact tagged
merge, then tests the Starter, clean-created projects, and reviewed Landing
consumer before public channel promotion and the Core GitHub Release. Starter
does not promote main, backport, or dispatch Landing.
Prepare the release PR
- Fetch Core, Starter, and Landing remotes. Prove the intended version and both tags are unused.
- Preview GitHub's generated notes since the previous tag. Correct PR metadata
and apply
skip-release-notesto the release-only PR. - Align every workspace package, plugin manifest, and marketplace ref to the exact version.
- Pin the controller to the reviewed Starter and Landing
developcommits, and Core CI to the same Starter commit. Never substitute a branch or floating tag. - Audit downstream literals when an SDK type or closed enum changed.
- Run:
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.
- 3d ago Changed · +5 lines 8e3c78ee7113
- 7d ago First seen · 95 lines · 0 tokens per session scan A 1caa33e4bb81
mantle-release is a skill published in the GitHub repository aotter/mantle (4 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 895 tokens. 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
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
bob-export
Create a Hacker Bob post-release improvement bundle for the currently installed Bob version.
oss-workflow
Open-source project success workflow for viznoir. Codifies contributor onboarding, release management (Release Please + PyPI), issue triage, and showcase curation. Triggers: release, contributor, onboarding, PyPI publish, issue triage, showcase, CHANGELOG, good first issue.