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 instructions/morooka-akira/aicm/05_development-rulesgit 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/instructions/morooka-akira/aicm/05_development-rules)<a href="https://agentmods.dev/instructions/morooka-akira/aicm/05_development-rules"><img src="https://agentmods.dev/badge/instructions/morooka-akira/aicm/05_development-rules.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.00662 | $0.00662 |
| Opus 5 | $0.00331 | $0.00331 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
aicm 05_development-rules.instructions.md 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.
What it actually says
開発ルール
タスクの進め方
-
- 作業開始時に、
ai-works/plansディレクトリにyyyy-mm-dd-<work name>_plan.mdを作成し、設計方針、完了要件をまとめてください
- 作業開始時に、
-
- 1のドキュメントに関してのTODOタスク一覧を
ai-works/todosディレクトリにyyyy-mm-dd-<work name>_todo.mdを作成してください。
- 1のドキュメントに関してのTODOタスク一覧を
-
- TODOに従って、作業を実行し、1つのTODOを完了させたら、必ずドキュメントを更新してください
中断からの再開
- 作業のコンテキストが足りない場合は、
yyyy-mm-dd-<work name>_plan.md,yyyy-mm-dd-<work name>_todo.mdを一度読み込み作業を再開してください - どのドキュメントを読めばよいか分からない場合は、作業を一度中断し、指示を仰いでください
タスク完了時
- rust コードに修正がある場合は、
cargo fmt,cargo clippyを実行してくださいcargo clippyは warning でも 修正してください
- 修正内容が、 @README.md @docs/ の内容と乖離がある場合は、ドキュメントの更新を行ってください
yyyy-mm-dd-<work name>_plan.mdの内容と実装に乖離がないか確認してくださいyyyy-mm-dd-<work name>_todo.mdのタスクが全て完了しているか確認し、更新してください- ルールに従って、PR を作成
- デフォルトブランチは
main - 作業開始時に、必ずデフォルトブランチからブランチを分けて作業すること
- 作業完了後は、gh コマンドで PR を作成すること
- デフォルトブランチは
テスト要件
- 必須: 各モジュールは Rust 標準テストフレームワークでテストを作成すること
- カバレッジ: 主要な機能とエラーパスのテストを含めること
- 作業完了: 作業終了時は必ずテストが通ることを確認すること
テスト実行例
# 全テスト実行
cargo test
# 特定のテストモジュール実行
cargo test config
cargo test agents::cursor
# テストカバレッジ（tarpaulin要インストール）
cargo install cargo-tarpaulin
cargo tarpaulin --out html
# 統合テスト実行
cargo test --test integration_test
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 · 47 lines · 662 tokens per session scan A e4aedfe123c4
aicm 05_development-rules.instructions.md is an instructions file published in the GitHub repository morooka-akira/aicm (6 stars, last pushed yesterday), licensed MIT. It adds 662 tokens to every session, about $0.0033 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.