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/nwiizo/cargo-coupling/releasenpx skills add nwiizo/cargo-coupling --skill releasegit clone --depth 1 https://github.com/nwiizo/cargo-couplingWrote 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/nwiizo/cargo-coupling/release)<a href="https://agentmods.dev/skills/nwiizo/cargo-coupling/release"><img src="https://agentmods.dev/badge/skills/nwiizo/cargo-coupling/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 | $0.00000 | $0.00231 |
| Opus 5 | $0.00000 | $0.00115 |
| Sonnet 5 | $0.00000 | $0.00046 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
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 2d 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 Skill
Steps for releasing a new version.
Pre-Release Checks
# Check formatting
cargo fmt --all -- --check
# Lint (treat warnings as errors)
cargo clippy --all-targets --all-features -- -D warnings
# Run tests
cargo test --all-features
# Verify release build
cargo build --release
Version Bump
- Update version in
Cargo.toml - Refresh
Cargo.lockwithcargo build --release - Commit with message:
chore: release vX.Y.Z
Release Commit
git add Cargo.toml Cargo.lock
git commit -m "chore: release vX.Y.Z"
git tag -a vX.Y.Z -m "vX.Y.Z"
git push origin main
git push origin vX.Y.Z
Automation
Pre-commit hook configured in .claude/settings.json runs:
cargo fmt --all --checkcargo clippy --all-targets --all-features -- -D warnings
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.
- 2d ago First seen · 42 lines · 0 tokens per session scan A 7cebf286631f
release is a skill published in the GitHub repository nwiizo/cargo-coupling (96 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 231 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-09-01.
Other skills, from other repositories
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-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
mate-oss-gate
在准备把 MateCloud（或其子集）开源 / 发布到公开仓前使用。按 open-core 边界把关：剥离企业代码、清竞品名与内部路径、查密钥、确认 LICENSE。当用户说"要开源了""发布公开版""开源前检查""oss release"时触发。.
snapshot-release
Drives the snapshot-release flow for the current branch's PR. Posts a /snapshot comment on the PR if one isn't already there (with confirmation), waits for the Continuous Releases workflow to finish, and reports the tarball URLs from the resulting 📦 Snapshot Release comment. Use for both triggering and waiting …
devops/changelog-generation
自动生成 CHANGELOG，基于 git 提交历史和 pipeline 产物信息，遵循 Conventional Commits 和 Keep a Changelog 规范.