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 sbom-tool/gh-guard --skill release-automationgit clone --depth 1 https://github.com/sbom-tool/gh-guardWrote 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/sbom-tool/gh-guard/release-automation)<a href="https://agentmods.dev/skills/sbom-tool/gh-guard/release-automation"><img src="https://agentmods.dev/badge/skills/sbom-tool/gh-guard/release-automation/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/sbom-tool/gh-guard/release-automation"><img src="https://agentmods.dev/badge/skills/sbom-tool/gh-guard/release-automation.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.01497 |
| Opus 5 | $0.00010 | $0.00749 |
| Sonnet 5 | $0.00004 | $0.00299 |
| Haiku 4.5 | $0.00002 | $0.00150 |
Grade C, and why
release-automation scanned grade C with 1 finding 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
git config --global user.signingkey ~/.ssh/id_ed25519.pub How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Automation for Rust Crates
This skill covers a PR-based release flow that works with branch protection rules, signed tags, and CI-triggered publishing.
Release Flow
Developer GitHub crates.io
│ │ │
├─ scripts/release.sh 0.2.0 │ │
│ │ │
├─ Local checks (deny, │ │
│ test, clippy, dry-run) │ │
│ │ │
├─ Create release/v0.2.0 ──→│ │
├─ Bump Cargo.toml ────────→│ │
├─ Push branch ────────────→│ │
├─ gh pr create ───────────→│── CI runs on PR │
│ │ │
├─ Poll for checks start │ │
├─ gh pr checks --watch ───→│── Waits for CI │
│ │ │
├─ gh pr merge ────────────→│── Squash merge │
├─ git pull origin main │ │
├─ git tag -s v0.2.0 ──────→│ │
├─ git push origin v0.2.0 ─→│── Tag push triggers: │
│ │ 1. publish (crates.io) ────→│
│ │ 2. provenance (SLSA L3) │
│ │ 3. release (GitHub) │
│ │ │
Pre-flight Checks
The release script verifies before doing anything:
- Version format — Must be valid semver
X.Y.Z - Signing key —
git config user.signingkeymust be set - Clean working tree — No uncommitted changes
- On main branch — Must be on
main - Up to date — Local HEAD matches
origin/main - Version not already set —
Cargo.tomlversion differs from target - Tag doesn't exist —
v${VERSION}tag not already present
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 · 171 lines · 19 tokens per session scan C 116884352336
release-automation is a skill published in the GitHub repository sbom-tool/gh-guard (15 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 1,497 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
cmux-release
Prefer the /release command. It determines the new version (minor by default), gathers commits since the last tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.