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.
git clone --depth 1 https://github.com/morooka-akira/aicmWrote 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/rules/morooka-akira/aicm/06_rust-rule)<a href="https://agentmods.dev/rules/morooka-akira/aicm/06_rust-rule"><img src="https://agentmods.dev/badge/rules/morooka-akira/aicm/06_rust-rule/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/rules/morooka-akira/aicm/06_rust-rule"><img src="https://agentmods.dev/badge/rules/morooka-akira/aicm/06_rust-rule.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.00010 | $0.00493 |
| Opus 5.5 | $0.00004 | $0.00197 |
| Sonnet 5.5 | $0.00002 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
06_rust-rule 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 1mo 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
rust 固有のルール
実装時の注意点
- 新しい機能を追加する際は、対応するテストも同時作成
- テストファイルは
#[cfg(test)]モジュールまたはtests/ディレクトリを使用 - エラーハンドリング（
Result<T, E>）も含めてテストケースを作成 - 非同期処理は
#[tokio::test]を使用してテスト
エラーハンドリング
- anyhow・thiserror による適切なエラー処理を行うこと
型システムの活用
serdeによる設定ファイルの型安全なデシリアライゼーションasync-traitによる非同期トレイトの実装thiserrorによる構造化されたエラー型定義- オプション型（
Option<T>）による明示的な Null 安全性
パフォーマンス特徴
- 高速起動: ネイティブバイナリによる瞬時起動（100ms 以内）
- 低メモリ: 効率的なメモリ管理（10MB 以下）
- 並列処理: 非同期 I/O による高速ファイル処理
- ゼロコピー: 不要な文字列コピーの回避
主要なクレート
- clap: CLI 構築フレームワーク（derive API 使用）
- tokio: 非同期ランタイム（full features）
- serde + serde_yaml: 設定ファイル処理
- anyhow + thiserror: エラーハンドリング
- async-trait: 非同期トレイト
- path-clean: パス正規化
- glob: パターンマッチング
開発用クレート
- tokio-test: 非同期テスト
- tempfile: テスト用一時ファイル
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.
- 1mo ago First seen · 48 lines · 10 tokens per session scan A 8a58caf1e394
06_rust-rule is a cursor rule published in the GitHub repository morooka-akira/aicm (6 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 493 once invoked, about $0.0000 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-08-31.
Other cursor rules, from other repositories
rust-module-refactor
Use when splitting Rust modules, moving tests, tightening visibility, or preserving facades during refactors.
rust-architect
PoolAI — Rust Architect workflow: runtime stack, MSYS2, target/ disk, pre-push checks, docs sync.
core
Core STT/TTS abstraction layer documentation.
arc-deref-pattern
When implementing parallel (Mt) algorithms in Verus, do NOT assume.
table-of-contents-standard
Standard section ordering and TOC format for Verus source files.
wrap-vs-specify
When to use externaltypespecification vs wrapper struct for Verus specs.