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/e2e-testgit 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/e2e-test)<a href="https://agentmods.dev/commands/nwiizo/cargo-coupling/e2e-test"><img src="https://agentmods.dev/badge/commands/nwiizo/cargo-coupling/e2e-test.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.00000 | $0.01180 |
| Opus 5 | $0.00000 | $0.00590 |
| Sonnet 5 | $0.00000 | $0.00236 |
| Haiku 4.5 | $0.00000 | $0.00118 |
Grade A, and why
e2e-test 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Test - End-to-End テスト実行
このコマンドは、cargo-coupling の機能を包括的にテストします。
使用方法
/e2e-test [オプション]
例:
/e2e-test
/e2e-test --quick
/e2e-test --verbose
テストシナリオ
1. 基本機能テスト
テスト用プロジェクトを /tmp/e2e-test-cargo-coupling に作成し、以下をテスト:
1.1 ネストされたモジュールパス (Issue #14)
src/
├── lib.rs
├── level/
│ ├── mod.rs
│ ├── projectile.rs
│ └── enemy/
│ ├── mod.rs
│ └── spawner.rs
期待結果: モジュール名が level::enemy::spawner のように正しく表示される(spawner だけではない)
1.2 テスト除外機能 (Issue #13)
// テスト関数を含むファイル
#[test]
fn test_something() {}
#[cfg(test)]
mod tests {
fn helper() {}
}
テスト:
--exclude-testsなし: テスト関数がカウントされる--exclude-testsあり: テスト関数が除外される
1.3 設定ファイル (.coupling.toml)
[analysis]
exclude_tests = true
prelude_modules = ["src/lib.rs", "src/prelude.rs"]
exclude = ["src/generated/*", "src/generated/**"]
exclude パターンは .coupling.toml を置いたディレクトリ基準で評価される。
2. 出力形式テスト
以下の出力形式をテスト:
- Markdown レポート(デフォルト)
- JSON 形式 (
--json) - サマリーモード (
--summary) - AI フレンドリー形式 (
--ai)
3. Web UI テスト (オプション)
--web オプションでサーバーが起動し、API エンドポイントが応答することを確認
実行手順
# 1. テスト用プロジェクト作成
mkdir -p /tmp/e2e-test-cargo-coupling/src/level/enemy
cd /tmp/e2e-test-cargo-coupling
# 2. Cargo.toml 作成
cat > Cargo.toml << 'EOF'
[package]
name = "e2e-test-project"
version = "0.1.0"
edition = "2021"
EOF
# 3. ソースファイル作成
# lib.rs, level/mod.rs, level/projectile.rs, level/enemy/mod.rs, level/enemy/spawner.rs
# 4. cargo-coupling 実行とアサーション
cargo run -- coupling /tmp/e2e-test-cargo-coupling/src
# 5. 結果検証
# - モジュールパスが正しいか
# - テスト除外が機能するか
# - 設定ファイルが読み込まれるか
検証項目チェックリスト
| テスト | 期待結果 | ステータス |
|---|---|---|
| ネストモジュールパス | level::enemy::spawner |
⬜ |
| lib.rs のモジュール名 | lib または空 |
⬜ |
| mod.rs のモジュール名 | 親ディレクトリ名 | ⬜ |
| --exclude-tests | テスト関数が除外 | ⬜ |
| .coupling.toml 読み込み | 設定が適用 | ⬜ |
| JSON 出力 | 有効な JSON | ⬜ |
| --summary | サマリーのみ出力 | ⬜ |
| --ai | AI フォーマット出力 | ⬜ |
出力フォーマット
# E2E テスト結果
## サマリー
- **テスト総数**: X
- **成功**: X
- **失敗**: X
- **スキップ**: X
## テスト結果詳細
### ✅ 成功したテスト
1. [テスト名]: [詳細]
### ❌ 失敗したテスト
1. [テスト名]: [期待値] vs [実際の値]
## 推奨アクション
[失敗がある場合の修正提案]
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 · 157 lines · 0 tokens per session scan A 865bc4f3b216
e2e-test is a command published in the GitHub repository nwiizo/cargo-coupling (96 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,180 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
e2e
使用 Playwright 对 Web UI 进行端到端测试(支持视频录制、Trace 录制、控制台/网络日志捕获).
verify
Run the right verification gates for what changed.
plan-spec
仅在人工明确安排 UI 自动化时,根据任务、产品规则或原型生成独立行为 Spec.
generate_application_test_plan
Khám phá ứng dụng web, sinh test plan và test scenarios. Hỗ trợ 2 mode — PLAN (chỉ test plan) và FULL (test plan + automation skeleton).
open
SoDam-Design-Kit open 대시보드 — 검증 이력·판정서·스크린샷을 브라우저로 열람 + 재검증.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.