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 commands/nwiizo/cargo-coupling/full-reviewgit 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/commands/nwiizo/cargo-coupling/full-review)<a href="https://agentmods.dev/commands/nwiizo/cargo-coupling/full-review"><img src="https://agentmods.dev/badge/commands/nwiizo/cargo-coupling/full-review.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.00000 | $0.01112 |
| Opus 5 | $0.00000 | $0.00556 |
| Sonnet 5 | $0.00000 | $0.00222 |
| Haiku 4.5 | $0.00000 | $0.00111 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Review - 総合アーキテクチャレビュー
このコマンドは、cargo-couplingによる分析と複数の専門家による総合レビューを実行します。
使用方法
/full-review [パス]
例:
/full-review ./src
/full-review .
実行フロー
Phase 1: 自動分析（5-10分）
-
cargo-coupling分析
cargo run -- coupling [パス] -
cargo clippy実行
cargo clippy --all-targets --all-features -- -D warnings -
cargo test実行
cargo test --all-features
Phase 2: 専門家レビュー（並列実行）
-
Balance Advisor（Vlad Khononov）
- カップリングバランスの評価
- 3次元分析（Strength, Distance, Volatility）
-
Architecture Critic（松本大輔）
- アーキテクチャリスクの評価
- 技術的負債の見積もり
-
Rust Idiomatic Expert（山田太郎）
- Rust慣用句の評価
- コード品質の確認
Phase 3: 統合レポート生成
すべてのレビュー結果を統合し、優先順位付きの改善提案を生成します。
出力フォーマット
# 総合アーキテクチャレビュー
**レビュー日時**: YYYY-MM-DD
**対象パス**: [パス]
---
## エグゼクティブサマリー
### 総合評価
**ヘルスグレード**: [A/B/C/D/F]
| 評価項目 | スコア | 判定 |
|---------|--------|------|
| カップリングバランス | X.XX/1.00 | [優秀/良好/要改善] |
| アーキテクチャリスク | X/10 | [低/中/高] |
| Rustイディオマティック | X.X/5.0 | [優秀/良好/要改善] |
| テスト合格率 | XX% | [合格/不合格] |
| Clippy警告 | X件 | [合格/要修正] |
### 一言総評
[プロジェクトの強みと主要な課題]
---
## Phase 1: 自動分析結果
### cargo-coupling
[分析結果サマリー]
### cargo clippy
[警告/エラー数と主要な内容]
### cargo test --all-features
[テスト結果サマリー]
---
## Phase 2: 専門家レビュー
### Balance Advisor（Vlad Khononov）
[カップリングバランス分析]
### Architecture Critic（松本大輔）
[アーキテクチャリスク評価]
### Rust Idiomatic Expert（山田太郎）
[Rustイディオマティック評価]
---
## 統合改善提案（優先度順）
### 🔴 Critical（今すぐ対応）
1. **[問題タイトル]**
- 影響: [何が問題か]
- アクション: [具体的な修正方法]
- 担当専門家: [誰の指摘か]
### 🟡 High（1週間以内に対応）
1. **[問題タイトル]**
- [...]
### 🟢 Medium（計画的に対応）
1. **[問題タイトル]**
- [...]
---
## 良い設計判断（維持すべき）
1. **[箇所]**: [何が良いか]
2. **[箇所]**: [何が良いか]
---
## 次のステップ
### 即時アクション
1. [最優先のアクション]
### 1週間後の目標
1. [中期目標]
### 長期改善計画
1. [長期目標]
---
## レビューチームからのメッセージ
**Vlad**: 「[バランスに関するアドバイス]」
**松本**: 「[アーキテクチャに関するアドバイス]」
**山田**: 「[Rustコードに関するアドバイス]」
実行時間の目安
- Phase 1（自動分析）: 1-3分
- Phase 2（専門家レビュー）: 5-10分
- Phase 3（統合レポート）: 1-2分
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 · 184 lines · 0 tokens per session scan A 01748408c526
full-review is a command published in the GitHub repository nwiizo/cargo-coupling (96 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,112 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.