Borrowing it
Nothing to install: this file belongs to tyler-mitchell/type-atlas. 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/tyler-mitchell/type-atlas/main/.skills/cli-release/SKILL.mdgit clone --depth 1 https://github.com/tyler-mitchell/type-atlasWrote 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/tyler-mitchell/type-atlas/cli-release)<a href="https://agentmods.dev/skills/tyler-mitchell/type-atlas/cli-release"><img src="https://agentmods.dev/badge/skills/tyler-mitchell/type-atlas/cli-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/tyler-mitchell/type-atlas/cli-release"><img src="https://agentmods.dev/badge/skills/tyler-mitchell/type-atlas/cli-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.00019 | $0.00348 |
| Opus 5.5 | $0.00008 | $0.00139 |
| Sonnet 5.5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
release-package 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.
What it actually says
Release packages
The root AGENTS.md owns branch, commit, push, and synchronization behavior.
For a consumer-visible package change, follow .skills/add-change/SKILL.md and
commit its bump file with the implementation on main. Bump files accumulate
until the ordinary main → release pull request merges; that push makes Bumpy
create or update bumpy/version-packages.
Create the bump with the first consumer-visible commit for that logical change. Update the same bump as the change evolves. Give unrelated logical changes separate bump files. Commit implementation, tests, generated consumer docs, and the bump together. Never wait for a release request to reconstruct bumps from commit history.
An explicit release request authorizes this sequence:
vp run dependencies:list
vp run dependencies:sync # after a dependency pull request merges
vp run release:push
vp run release:promote:pr
vp run release:promote:create # only when no promotion pull request exists
vp run release:promote:merge
After GitHub reports the promotion merge, run:
vp run release:pr
vp run release:merge
Run release:merge only when release:pr returns the version pull request.
Required checks gate both merges. GitHub owns publication and public
verification. After publication, run release:sync and release:sync:push on
the clean main branch. Inspect a workflow only after failure. Never version,
publish, dispatch, or poll locally.
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 · 44 lines · 19 tokens per session scan A 94ace04b3767
release-package is a skill published in the GitHub repository tyler-mitchell/type-atlas (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 348 once invoked, about $0.0001 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-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). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
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, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
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…
studio-source-control
Drive a scoped application's linked git repository from the instance — what has to be true before Source Control works at all, the commit-then-push order, stashes and branches over /api/snsourcecontrol, and when this replaces update sets rather than sitting next to them.