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/webnpx skills add nwiizo/cargo-coupling --skill webgit 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/web)<a href="https://agentmods.dev/skills/nwiizo/cargo-coupling/web"><img src="https://agentmods.dev/badge/skills/nwiizo/cargo-coupling/web.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.00021 | $0.00513 |
| Opus 5 | $0.00010 | $0.00257 |
| Sonnet 5 | $0.00004 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
web 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
Web - Visualization UI
Start
cargo build --release
cargo run --release -- coupling --web $ARGUMENTS # default: ./src
# Custom port
cargo run --release -- coupling --web --port 8080 ./src
# Don't auto-open browser
cargo run --release -- coupling --web --no-open ./src
# Web timeline uses the same history sampling model as --history
cargo run -- coupling --history=8 --git-months=12 ./src
Keyboard Shortcuts
| Key | Action |
|---|---|
/ |
Focus search |
f |
Fit to screen |
r |
Reset layout |
e |
Export PNG |
Esc |
Clear selection |
? |
Show help |
Graph Interaction
- Click node: Highlight neighbors, center view
- Click edge: Show dependency direction
- Click background: Clear selection
Panel Features
2D / 3D Graphs
Explore coupling relationships in 2D or 3D views.
Dimension-Space
Inspect strength, distance, volatility, and balance score as separate trust dimensions.
Timeline
Shows coupling health across git revisions with auto-play controls.
Trust
Shows analysis confidence, run notes, and declared blind spots.
Hotspots
Top refactoring targets ranked by severity. Click to jump.
Key Modules
- Connections: Sort by dependency count
- Issues: Sort by problem count
- Health: Sort by health score
Analysis
- Show Dependents: Modules depending on selected
- Show Dependencies: Modules selected depends on
- Full Impact: Complete blast radius
Filters
- Strength: Intrusive / Functional / Model / Contract
- Distance: SameFunction / SameModule / DifferentModule / DifferentCrate
- Volatility: High / Medium / Low
- Balance Score: Range filter
- Show Issues Only / Show Cycles Only
Export
- PNG Image: Save graph as image
- JSON Data: Save analysis data as JSON
Notes
- Ctrl+C to stop server
- Large projects may take longer on initial load
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 · 86 lines · 0 tokens per session scan A a0f6a16f970c
web is a skill published in the GitHub repository nwiizo/cargo-coupling (96 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 513 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…