cargo-coupling: Instructions file for Claude Code

CLAUDE.md

cargo-coupling CLAUDE.md is an instructions file for Claude Code from nwiizo/cargo-coupling. It costs 1,532 tokens per session, scanned A, original, MIT.

Project instructions for cargo-coupling, a Rust command-line tool for measuring coupling and checking changes against Git references.

In plain words
What is it for?
Use them when developing cargo-coupling, running its analysis or web UI, configuring CI quality gates, or preparing releases.
Why use it?
They tell an agent how to build, test, format, lint, run, containerize, and release the project correctly.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions Claude Code.

This is nwiizo/cargo-coupling's own configuration. It tells Claude Code how to work on cargo-coupling itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cargo-coupling configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/nwiizo/cargo-coupling/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/nwiizo/cargo-coupling

Made for: Claude Code.

Wrote 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.

agentmods badge for cargo-coupling CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/nwiizo/cargo-coupling/claude-md/github.svg)](https://agentmods.dev/instructions/nwiizo/cargo-coupling/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/nwiizo/cargo-coupling/claude-md"><img src="https://agentmods.dev/badge/instructions/nwiizo/cargo-coupling/claude-md/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.

agentmods 80×15 button for cargo-coupling CLAUDE.md

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,532 This file is loaded in full into every session.
When invoked 1,532 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01532 $0.01532
Opus 5.5 $0.00613 $0.00613
Sonnet 5.5 $0.00306 $0.00306
Haiku 4.5 $0.00153 $0.00153

Measured 20d ago against content hash 55a79d32d414, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

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.

CLAUDE.md · 115 lines

How it starts

The opening of the file, as written. The whole thing — 115 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

Read the full file on GitHub · 115 lines

Changes

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.

  1. 20d ago Changed · +1 lines · +25 tokens per session 55a79d32d414
  2. 1mo ago First seen · 114 lines · 1,507 tokens per session scan A 5ce8c2ec1493

Subscribe to this mod's changes

cargo-coupling CLAUDE.md is an instructions file published in the GitHub repository nwiizo/cargo-coupling (116 stars, last pushed 2d ago), licensed MIT. It adds 1,532 tokens to every session, about $0.0061 per session on Opus 5.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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens