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/03_project-architecture)<a href="https://agentmods.dev/rules/morooka-akira/aicm/03_project-architecture"><img src="https://agentmods.dev/badge/rules/morooka-akira/aicm/03_project-architecture.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.00537 | $0.00537 |
| Opus 5 | $0.00269 | $0.00269 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
03_project-architecture 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 7d 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 の型システムによるコンパイル時エラー検出
- メモリ安全性: 所有権システムによる安全なメモリ管理
- 並行処理: Tokio による効率的な非同期処理
- 抽象化: トレイトベースのエージェント設計
- 統一管理: 共通の設定ファイルから各ツール用ファイルを生成
プロジェクト構造
src/
├── main.rs # CLI エントリーポイント
├── lib.rs # ライブラリエントリーポイント
├── config/ # 設定管理
│ ├── mod.rs
│ ├── loader.rs # 設定読み込み
│ └── error.rs # 設定エラー型
├── core/ # コア機能
│ ├── mod.rs
│ └── markdown_merger.rs # Markdownファイル結合
├── agents/ # エージェント実装
│ ├── mod.rs
│ ├── base.rs # ベースユーティリティ
│ ├── cursor.rs # Cursor実装（実装済み）
│ ├── cline.rs # Cline実装（実装済み）
│ ├── github.rs # GitHub Copilot実装（実装済み）
│ └── claude.rs # Claude実装（実装済み）
└── types/ # 型定義
├── mod.rs
├── config.rs # 設定型
└── agent.rs # エージェント型
docs/ # 設計ドキュメント
├── concept.md # 設計概要
├── design_doc.md # 技術仕様書（Rust版）
└── requirements.md # 要件定義
target/ # ビルド出力
├── debug/ # デバッグビルド
└── release/ # リリースビルド
Cargo.toml # プロジェクト設定
Cargo.lock # 依存関係ロック
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.
- 7d ago First seen · 54 lines · 537 tokens per session scan A abe7f6ce3ed3
03_project-architecture is a cursor rule published in the GitHub repository morooka-akira/aicm (6 stars, last pushed today), licensed MIT. It adds 537 tokens to every session, about $0.0027 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-08-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.