icm: Instructions file for Codex

AGENTS.md

icm AGENTS.md is an instructions file for Codex, OpenCode from rtk-ai/icm. It costs 357 tokens per session, scanned A, original, Apache-2.0.

Instructions for using ICM, a persistent memory tool that lets an AI agent recall information across sessions. They define when the agent must search memory and save new decisions or results.

In plain words
What is it for?
Use them at the start of work to recall context and after major decisions, solved errors, user preferences, or completed tasks to store a summary.
Why use it?
They reduce repeated work by bringing back relevant past context and ensure important decisions, preferences, and resolved errors are not lost.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md.

This is rtk-ai/icm's own configuration. It tells Codex and OpenCode how to work on icm 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 icm configures →

View source ↗ rtk-ai/icm
Reuse

Borrowing it

Nothing to install: this file belongs to rtk-ai/icm. 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/rtk-ai/icm/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/rtk-ai/icm

Made for: Codex, OpenCode.

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 icm AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/rtk-ai/icm/agents-md/github.svg)](https://agentmods.dev/instructions/rtk-ai/icm/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/rtk-ai/icm/agents-md"><img src="https://agentmods.dev/badge/instructions/rtk-ai/icm/agents-md/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 icm AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/rtk-ai/icm/agents-md"><img src="https://agentmods.dev/badge/instructions/rtk-ai/icm/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 357 This file is loaded in full into every session.
When invoked 357 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.00357 $0.00357
Opus 5.5 $0.00143 $0.00143
Sonnet 5.5 $0.00071 $0.00071
Haiku 4.5 $0.00036 $0.00036

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

Security

Grade A, and why

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

AGENTS.md · 33 lines

What it actually says

Persistent memory (ICM) — MANDATORY

This project uses ICM for persistent memory across sessions. You MUST use it actively. Not optional.

Recall (before starting work)

icm recall "query"                        # search memories
icm recall "query" -t "topic-name"        # filter by topic
icm recall-context "query" --limit 5      # formatted for prompt injection

Store — MANDATORY triggers

You MUST call icm store when ANY of the following happens:

  1. Error resolved → icm store -t errors-resolved -c "description" -i high -k "keyword1,keyword2"
  2. Architecture/design decision → icm store -t decisions-{project} -c "description" -i high
  3. User preference discovered → icm store -t preferences -c "description" -i critical
  4. Significant task completed → icm store -t context-{project} -c "summary of work done" -i high
  5. Conversation exceeds ~20 tool calls without a store → store a progress summary

Do this BEFORE responding to the user. Not after. Not later. Immediately.

Do NOT store: trivial details, info already in CLAUDE.md, ephemeral state (build logs, git status).

Other commands

icm update <id> -c "updated content"     # edit memory in-place
icm health                                # topic hygiene audit
icm topics                                # list all topics
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 · 33 lines · 357 tokens per session scan A 73e0a225e0fd

Subscribe to this mod's changes

icm AGENTS.md is an instructions file published in the GitHub repository rtk-ai/icm (598 stars, last pushed today), licensed Apache-2.0. It adds 357 tokens to every session, about $0.0014 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-30.

Related

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

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

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens