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/arkatom/ai-instructions/claude-mdgit clone --depth 1 https://github.com/arkatom/ai-instructionsWrote 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/arkatom/ai-instructions/claude-md)<a href="https://agentmods.dev/instructions/arkatom/ai-instructions/claude-md"><img src="https://agentmods.dev/badge/instructions/arkatom/ai-instructions/claude-md.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.01031 | $0.01031 |
| Opus 5 | $0.00515 | $0.00515 |
| Sonnet 5 | $0.00206 | $0.00206 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
ai-instructions CLAUDE.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 3d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI開発指示
🎯 核心原則（必須読込）
品質基準
- 品質優先: 速さより正確性と完全性
- 深層思考: 表面的な理解を避け、本質を把握
- 価値提供: 期待を超える成果を目指す
実行フロー
- 分析 → 要求の本質を理解
- 計画 → 最適なアプローチを選択
- 実装 → 品質基準を満たす実行
- 検証 → 結果の妥当性を確認
📚 必須参照
コア指示（常時適用）
場面別指示（自動判断）
| 場面 | 参照ファイル | 適用条件 |
|---|---|---|
| Git操作 | Git運用 | commit/PR/branch操作時 |
| TDD開発 | TDD手法 | テスト駆動開発時 |
| Issue管理 | Issue駆動 | Issue関連作業時 |
| デバッグ | デバッグ思考 | 問題調査・原因分析時 |
| 協働作業 | 協働インターフェース | 人間/AI間の情報交換時 |
失敗防止ガイド（常時参照）
| 技術 | 参照ファイル | 重要度 |
|---|---|---|
| TypeScript | TypeScript失敗防止 | 必須 |
| React | React失敗防止 | 必須 |
| JavaScript | JavaScript失敗防止 | 必須 |
| Python | Python失敗防止 | 必須 |
| Testing | テスト失敗防止 | 必須 |
🔧 ツール活用
優先順位
- 専用ツール → 利用可能なら最優先
- エージェント → 複雑なタスクは適切に委任
- コマンド → ツールがない場合のみ
記録管理
- 重要事項 → Issue/memoryに記録
- 作業記録 → ノート形式で保存
⚠️ 重要制約
してはいけないこと
- コード重複・散在
- 不要ファイルの放置
- 表面的な理解での実装
- 適当な推測や仮定
必ずすること
- 参照確認:
✅:{filename.md}を出力 - 適当度評価: 1-10で自己評価（5以上なら再考）
- 完全性確認: ユーザーが追加質問不要な状態
📂 構造規約
project/
├── docs/ # ドキュメント集約
├── instructions/ # AI指示（このファイル群）
│ ├── core/ # 思考プロセス
│ ├── guidelines/ # 失敗防止ガイド
│ └── methodologies/ # 開発手法
├── references/ # 実装例（人間向け）
│ └── patterns/ # 具体的実装パターン
└── src/ # ソースコード
🎨 patterns/について
references/patterns/配下のファイルは開発者向けリファレンスです。
AIは必要と判断した場合のみ参照してください。
過度な具体例への依存は創造性を制限します。
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.
- 3d ago First seen · 91 lines · 1,031 tokens per session scan A f65bf198fe07
ai-instructions CLAUDE.md is an instructions file published in the GitHub repository arkatom/ai-instructions (1 stars, last pushed 9mo ago), licensed MIT. It adds 1,031 tokens to every session, about $0.0052 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.