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/agiletec-inc/cmd-ime/claude-mdgit clone --depth 1 https://github.com/agiletec-inc/cmd-imeWrote 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/agiletec-inc/cmd-ime/claude-md)<a href="https://agentmods.dev/instructions/agiletec-inc/cmd-ime/claude-md"><img src="https://agentmods.dev/badge/instructions/agiletec-inc/cmd-ime/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.00561 | $0.00561 |
| Opus 5 | $0.00280 | $0.00280 |
| Sonnet 5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
cmd-ime 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 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
CmdIME
左右Command keyなどをIME入力へ割り当てるnative macOS menu bar app。version正本はmanifest.toml。
build/test/release commandはpackage manifest、Makefile、workflowから読む。
推測できない境界
- CGEvent hot pathは
shortcutList、exclusionAppsDict等のglobal cacheを読む。設定の正本は@MainActor AppSettings.sharedで、cacheは設定変更時に同期する。hot pathからUserDefaultsを読まない。 - keyCode
999はswallow、1000+はmedia key。54/55は左右Command、102/104は英数/かな。意味を通常keyへ 正規化しない。 - macOSはinput source変更等でevent tapを無効化する。heartbeat、Accessibility付与後retry、brew upgrade時の bundle置換監視を維持する。
- release appcastは専用
appcastbranchが配信正本。mainのappcast.xmlは空seedであり履歴を追記しない。 - native appなのでDockerを使わない。release signing/notarizationとlocal ad-hoc buildを混同しない。
- ユーザー向け文字列は必ず
L(_:)(Sources/CmdIMESwift/Localization.swift)経由。swift build/swift testはLocalizable.xcstringsをコンパイルしない(Xcode専用機能)ため、Sources/CmdIMESwift/Resources/<locale>.lproj/ Localizable.stringsをxcstringstool compileで事前コンパイルして正本と一緒にcommitする。文字列を追加・変更したらxcrun xcstringstool compile Sources/CmdIMESwift/Resources/Localizable.xcstrings --output-directory Sources/CmdIMESwift/Resources --serialization-format textで再生成し、LocalizationCatalogTestsのdriftチェックを green にしてからcommitする。scripts/package.shはSPMの<Package>_<Target>.bundleをContents/Resources/へ 手動でdittoする一文が要る — 標準のswift build -c releaseだけでは.appにリソースが同梱されない。
変更後はSwift test、build、必要ならevent tap/Accessibilityの実機確認を行う。コメントは周囲の密度と言語へ合わせる。
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 · 25 lines · 561 tokens per session scan A 08c1832d328c
cmd-ime CLAUDE.md is an instructions file published in the GitHub repository agiletec-inc/cmd-ime (13 stars, last pushed 5d ago), licensed MIT. It adds 561 tokens to every session, about $0.0028 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.