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/.claude/skills/check-balance/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/check-balance)<a href="https://agentmods.dev/skills/nwiizo/cargo-coupling/check-balance"><img src="https://agentmods.dev/badge/skills/nwiizo/cargo-coupling/check-balance/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/check-balance"><img src="https://agentmods.dev/badge/skills/nwiizo/cargo-coupling/check-balance.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.00022 | $0.00417 |
| Opus 5 | $0.00011 | $0.00209 |
| Sonnet 5 | $0.00004 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
check-balance 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 8d 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
Check Balance - Quick Health Check
Execution Steps
- Run
cargo run -- coupling --summary $ARGUMENTS(default:./src) - Check balance score and health grade
- Provide brief advice if issues detected
Commands
# Summary check
cargo run -- coupling --summary ./src
# Japanese output
cargo run -- coupling --summary --japanese ./src
# CI/CD quality gate
cargo run -- coupling --check --min-grade=C ./src
# Ratchet gate against a baseline ref
cargo run -- coupling --check --baseline main --fail-on=high ./src
# Coupling health over git history
cargo run -- coupling --history ./src
Health Grades
| Score | Grade | Status | Action |
|---|---|---|---|
| 0.90-1.00 | A | Excellent | Maintain |
| 0.80-0.89 | B | Good | Minor improvements |
| 0.60-0.79 | C | Acceptable | Planned improvement |
| 0.40-0.59 | D | Needs improvement | Act soon |
| 0.00-0.39 | F | Critical | Immediate action |
Issue Severity
| Severity | Action |
|---|---|
| Critical | Fix immediately |
| High | Fix within 1 week |
| Medium | Plan to fix |
| Low | Monitor |
Ratchet Mode
cargo run -- coupling --check --baseline <ref> ./src compares current issues against the baseline ref and fails only on new issues at --fail-on severity or higher. The default ratchet threshold is High/Critical.
Next Steps
- Low score: Run
/analyzefor details - Critical issues: Run
/full-reviewfor comprehensive analysis
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.
- 8d ago First seen · 61 lines · 22 tokens per session scan A 45bce128ce79
check-balance is a skill published in the GitHub repository nwiizo/cargo-coupling (96 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 417 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-09-01.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.