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/hotspotsnpx skills add nwiizo/cargo-coupling --skill hotspotsgit 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/hotspots)<a href="https://agentmods.dev/skills/nwiizo/cargo-coupling/hotspots"><img src="https://agentmods.dev/badge/skills/nwiizo/cargo-coupling/hotspots.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.1 | $0.00024 | $0.00365 |
| Opus 5 | $0.00012 | $0.00182 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
hotspots 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 4d 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
Hotspots - Refactoring Priority
Execution Steps
- Run
cargo run --release -- coupling --ai $ARGUMENTS(default:./src) - Calculate hotspot score for each module
- Display ranked list with recommendations
Commands
# Default (top 5)
cargo run -- coupling --hotspots ./src
# Top 10
cargo run -- coupling --hotspots=10 ./src
# With explanations
cargo run -- coupling --hotspots --verbose ./src
Scoring Formula
| Factor | Weight | Description |
|---|---|---|
| Issue count | x30 | Number of coupling issues |
| Coupling count | x5 | In/out dependency count |
| Health: Critical | +50 | Critical health status |
| Health: Needs Review | +20 | Needs review status |
| Circular dependency | +40 | Part of a cycle |
Output Format
## Refactoring Hotspots
### 1. [Module] (Score: XX)
- **Issues**: [Types and count]
- **Coupling**: In X / Out Y
- **Recommended action**: [Specific improvement]
Analysis Dimensions
- Why problematic — Issue types, coupling patterns
- Priority — Blast radius, difficulty, expected benefit
- Refactoring proposals — Interface separation, dependency inversion, module splitting, facade
Notes
- Score 0 = no issues
- Circular dependencies = highest priority
- Focus on top 5 for actionable results
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.
- 4d ago First seen · 60 lines · 24 tokens per session scan A 691e74986a29
hotspots is a skill published in the GitHub repository nwiizo/cargo-coupling (96 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 365 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…