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 instructions/nwiizo/cargo-coupling/claude-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/instructions/nwiizo/cargo-coupling/claude-md)<a href="https://agentmods.dev/instructions/nwiizo/cargo-coupling/claude-md"><img src="https://agentmods.dev/badge/instructions/nwiizo/cargo-coupling/claude-md.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.01507 | $0.01507 |
| Opus 5 | $0.00754 | $0.00754 |
| Sonnet 5 | $0.00301 | $0.00301 |
| Haiku 4.5 | $0.00151 | $0.00151 |
Grade A, and why
cargo-coupling CLAUDE.md 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cargo-coupling
Rust CLI for coupling analysis based on Khononov's "Balancing Coupling in Software Design".
Commands
# Development
cargo build --release && cargo test --all-features && cargo fmt --all && cargo clippy --all-targets --all-features -- -D warnings
# Run
cargo run -- coupling ./src # Analyze
cargo run -- coupling --web ./src # Web UI (:3000)
cargo run -- coupling --history ./src # Coupling health over git history (time-series)
cargo run -- coupling --history=8 --json ./src # Time-series as JSON (8 samples)
cargo run -- coupling --baseline main ./src # Diff current issues against a git ref
cargo run -- coupling --check --baseline main ./src # Ratchet gate: fail only on new High/Critical issues
# Docker
docker build -t cargo-coupling .
docker run --rm -v $(pwd):/workspace cargo-coupling coupling /workspace/src
docker compose up web
# Release
cargo fmt --all -- --check
cargo clippy --all-targets --all-features -- -D warnings
cargo test --all-features
cargo build --release
# bump Cargo.toml to X.Y.Z, refresh Cargo.lock, then:
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
# → GitHub Actions auto-publishes to crates.io
# Docker Release (manual)
gh auth refresh -h github.com -s write:packages
gh auth token | docker login ghcr.io -u nwiizo --password-stdin
docker build -t ghcr.io/nwiizo/cargo-coupling:vX.Y.Z -t ghcr.io/nwiizo/cargo-coupling:latest .
docker push ghcr.io/nwiizo/cargo-coupling:vX.Y.Z
docker push ghcr.io/nwiizo/cargo-coupling:latest
Key Files
| Path | Purpose |
|---|---|
src/analyzer.rs |
AST analysis (syn) |
src/discovery.rs |
Source file discovery (cargo targets + module tree, #[path]) |
src/classification.rs |
Coupling classification: target resolution, structural distance, strength |
src/balance/ |
Balance score calculation and issue detection |
src/metrics/ |
Data structures (ProjectMetrics, dimensions) |
src/history.rs |
Time-series: re-analyzes past git revisions via worktrees (--history) |
src/config.rs |
.coupling.toml loading and pattern compilation |
src/workspace.rs |
cargo metadata / workspace resolution |
src/web/ |
Web visualization server |
Dockerfile |
distroless (58MB) |
Dockerfile.full |
debian-slim + Git |
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.
- 3d ago First seen · 114 lines · 1,507 tokens per session scan A 5ce8c2ec1493
cargo-coupling CLAUDE.md is an instructions file published in the GitHub repository nwiizo/cargo-coupling (96 stars, last pushed 6d ago), licensed MIT. It adds 1,507 tokens to every session, about $0.0075 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 instructions, from other repositories
cli AGENTS.md
AGENTS.md instructions for googleworkspace/cli, covering agents.md, project overview, build & test, changesets and architecture.
turso AGENTS.md
AGENTS.md instructions for tursodatabase/turso, covering turso agent guidelines, quick reference, testing, running tests and test organization.
azure-sdk-for-rust resourcemanager.instructions.md
Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
bifrost AGENTS.md
AGENTS.md instructions for bifrost-proxy/bifrost, covering bifrost 项目开发规则, 执行心法, 执行模式与完成定义, 任务模式判定 and 变更类型与验证路由(先判定,后执行).
ton-rs AGENTS.md
AGENTS.md instructions for ston-fi/ton-rs, covering ton-rs agent guide, repository, boundaries, public api and ton invariants.