Borrowing it
Nothing to install: this file belongs to nwiizo/cargo-coupling. 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/nwiizo/cargo-coupling/main/.agents/skills/release/SKILL.mdgit 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/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/nwiizo/cargo-coupling/release"><img src="https://agentmods.dev/badge/skills/nwiizo/cargo-coupling/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00034 | $0.00429 |
| Opus 5.5 | $0.00014 | $0.00172 |
| Sonnet 5.5 | $0.00007 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade B, and why
release scanned grade B 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 20d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
The optional Claude hook in [.claude/settings.json](../../../.claude/settings.json) checks What it actually says
Release cargo-coupling
Match the requested version and publication scope. A preparation request ends with verified local artifacts; a publish request includes the authorized release commit, tag, push, and publication verification. Carry existing authorization forward. Resolve a missing version before changing release metadata; meanwhile inspect the branch, remote, status, and current release workflow.
Update Cargo.toml and refresh Cargo.lock without upgrading unrelated dependencies.
Run the required checks against the final release state:
rtk cargo fmt --all -- --check
rtk cargo clippy --locked --all-targets --all-features -- -D warnings
rtk cargo test --locked --all-features
rtk cargo build --locked --release
Before publication, verify the staged diff, intended branch and remote, matching
manifest/lockfile versions, and that the tag does not already identify a different
release. Preserve unrelated work. Use an annotated vX.Y.Z tag on the verified
release commit; the commit message is chore: release vX.Y.Z. Push only the intended
branch and tag to the verified remote; never replace an existing release tag.
Pushing a v* tag triggers .github/workflows/release.yml,
which publishes to crates.io and creates a GitHub release. Check both outcomes
before reporting publication complete. If publication fails or is uncertain,
inspect the workflow and registry state before retrying; do not create another
version or move a tag to bypass the failure.
The optional Claude hook in .claude/settings.json checks formatting and lint for matching commit commands. It does not establish that all release checks ran in another host. Reuse successful current checks while the release state is unchanged.
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.
- 20d ago Changed · +16 tokens per session scan A → B 4285804e247c
- 1mo ago Changed · -1 lines · +18 tokens per session cb91f7a70c95
- 1mo ago First seen · 42 lines · 0 tokens per session scan A 7cebf286631f
release is a skill published in the GitHub repository nwiizo/cargo-coupling (116 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 429 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other skills, from other repositories
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
release
Evaluate readiness and publish to crates.io.
cargo-release
PM-invocable protocol for Cargo publish and release operations in the trusty-tools Rust monorepo: semver rules, 10-step release sequence, macOS codesign safety, and cross-crate dependency ordering.
cargo-publish
Operate the socket-release crates.io flow - the cargo staged model (dry-run default), trusted publishing via OIDC under the cargo-publish environment, index-propagation waits, and yank-as-rollback. Use when publishing a Rust crate in a repo carrying scripts/socket-release/.
publish-rust
Verify and release a Rust crate or workspace. Bumps version, commits, tags, pushes. CI-driven by default; --local publishes directly.
jackin-release
Use only when the user explicitly requests this skill. Cuts a jackin❯ release — runs the readiness gates, writes the changelog, recommends a version, then executes cargo release on explicit operator confirmation.