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 agentmods add skills/logosdx/monorepo/release-workflownpx skills add logosdx/monorepo --skill release-workflowgit clone --depth 1 https://github.com/logosdx/monorepoWrote 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/logosdx/monorepo/release-workflow)<a href="https://agentmods.dev/skills/logosdx/monorepo/release-workflow"><img src="https://agentmods.dev/badge/skills/logosdx/monorepo/release-workflow.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 | $0.00025 | $0.00442 |
| Opus 5 | $0.00013 | $0.00221 |
| Sonnet 5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
release-workflow 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 4d 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 Workflow
Quick Start
# From a feature branch with changes ready:
/release-workflow
Critical Rules
- Must be on feature branch - Not master/main. Create branch first if needed.
- Session reports drive changesets - Reads
tmp/reports/new/for context. - Two-phase process - First: changesets + commit. Second: automated PR flow.
- Script handles git/github -
release.mjsautomates CI waits and merges.
Workflow
- Read session reports from
tmp/reports/new/to understand changes - Invoke
/changeset-writerskill to create changesets - Invoke
/git-committerskill to commit all changes - Run
pnpm zx .claude/skills/release-workflow/release.mjsto automate:- Push branch, create PR to master
- Wait for CI, merge PR (squash)
- Wait for Version Packages PR, merge it
- The version bump on master triggers the publish workflow; wait for it
Manual Steps (if script fails)
| Step | Command |
|---|---|
| Push & PR | git push -u origin HEAD && gh pr create --base master --fill |
| Watch CI | gh run watch $(gh run list -b BRANCH -L1 --json databaseId -q '.[0].databaseId') |
| Merge PR | gh pr merge --squash --delete-branch |
| Version PR | gh pr list --search "Version Packages" then gh pr merge NUM --squash |
| Watch publish | gh run watch $(gh run list -b master -w publish.yml -L1 --json databaseId -q '.[0].databaseId') |
References
- release.mjs - Automated workflow script
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.
- 4d ago First seen · 49 lines · 25 tokens per session scan A 4fc9e821c9b6
release-workflow is a skill published in the GitHub repository logosdx/monorepo (7 stars, last pushed 19d ago), licensed BSD-3-Clause. It adds 25 tokens to every session and 442 once invoked, about $0.0001 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…