aicm: Instructions file for GitHub Copilot

.github/instructions/05_development-rules.instructions.md

aicm 05_development-rules.instructions.md is an instructions file for GitHub Copilot from morooka-akira/aicm. It costs 662 tokens per session, scanned A, original, MIT.

A development workflow guide written in Japanese for a Rust project. It requires written plans and task lists, regular documentation updates, testing, code checks, and pull requests.

In plain words
What is it for?
Use it to create plan and TODO files, run Rust formatting, warnings checks, and tests, update documentation, work from a branch based on `main`, and open a pull request.
Why use it?
It gives developers a record of the work in progress and clear checks for finishing a change, including work that resumes after an interruption.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is morooka-akira/aicm's own configuration. It tells GitHub Copilot how to work on aicm itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything aicm configures →

Reuse

Borrowing it

Nothing to install: this file belongs to morooka-akira/aicm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/morooka-akira/aicm/main/.github/instructions/05_development-rules.instructions.md
Clone the repo
git clone --depth 1 https://github.com/morooka-akira/aicm

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for aicm 05_development-rules.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/morooka-akira/aicm/05_development-rules/github.svg)](https://agentmods.dev/instructions/morooka-akira/aicm/05_development-rules)
Your own site
<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/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.

agentmods 80×15 button for aicm 05_development-rules.instructions.md

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 662 This file is loaded in full into every session.
When invoked 662 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00662 $0.00662
Opus 5.5 $0.00265 $0.00265
Sonnet 5.5 $0.00132 $0.00132
Haiku 4.5 $0.00066 $0.00066

Measured 1mo ago against content hash e4aedfe123c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.github/instructions/05_development-rules.instructions.md · 47 lines

What it actually says

開発ルール

タスクの進め方

    1. 作業開始時に、ai-works/plans ディレクトリに yyyy-mm-dd-<work name>_plan.md を作成し、設計方針、完了要件をまとめてください
    1. 1のドキュメントに関してのTODOタスク一覧を ai-works/todos ディレクトリに yyyy-mm-dd-<work name>_todo.md を作成してください。
    1. 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
Changes

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.

  1. 1mo ago First seen · 47 lines · 662 tokens per session scan A e4aedfe123c4

Subscribe to this mod's changes

aicm 05_development-rules.instructions.md is an instructions file published in the GitHub repository morooka-akira/aicm (6 stars, last pushed today), licensed MIT. It adds 662 tokens to every session, about $0.0026 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.

Related

Other instructions, from other repositories

flow-like copilot-instructions.md

Copilot instructions for Rheosoph/flow-like, covering flow-like wasm node development — rust, project overview, build & test, architecture and pin types.

Rheosoph/flow-like · 1,349 tokens

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).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens