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/.agents/skills/coupling-full-review/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/coupling-full-review)<a href="https://agentmods.dev/skills/nwiizo/cargo-coupling/coupling-full-review"><img src="https://agentmods.dev/badge/skills/nwiizo/cargo-coupling/coupling-full-review/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/coupling-full-review"><img src="https://agentmods.dev/badge/skills/nwiizo/cargo-coupling/coupling-full-review.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.00333 |
| Opus 5.5 | $0.00014 | $0.00133 |
| Sonnet 5.5 | $0.00007 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
coupling-full-review 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.
What it actually says
Full Architecture Review
Review the requested scope (default ./src) and produce evidence-backed priorities.
Use coupling-review for coupling analysis, then inspect the relevant
architecture boundaries and Rust implementation. Reuse current analysis results.
Consider coupling balance, architectural change risks, and Rust idioms as review perspectives. Apply each where it can reveal a consequential problem; named personas, separate agents, numeric expert scores, and fixed schedules are not required. Delegate only when the user or applicable instructions request delegation, with a bounded subtask for each agent.
Use history or a baseline when the question concerns trends or a PR. Run tests, lint, or structural diagnostics when needed to substantiate findings or required by repository policy. Report which checks actually ran and any missing coverage; do not run duplicate output modes or repeat unchanged passing checks as phases.
Consolidate findings with source locations, impact, confidence, and concrete next actions. Separate automated signals from conclusions verified in code. Preserve good boundaries, stable hubs, and the analysis blind spots. Use the report example when a structured report helps, adapting it to the request and omitting unsupported scores or empty sections.
Complete the review with supported findings and limits. If fixes are also requested, apply and verify the agreed scope without treating the report as a mandatory pause.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 20d ago First seen · 32 lines · 35 tokens per session scan A 5bcf19d94122
coupling-full-review is a skill published in the GitHub repository nwiizo/cargo-coupling (116 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 333 once invoked, about $0.0001 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-10-09.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…