example

A rules example that points to a configuration file and a JSON data file. JSON is a text format commonly used to store structured data.

In plain words
What is it for?
Teaching an agent to consult the referenced config file and data file.
Why use it?
It shows where an agent should look for configuration and data-format details.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/ranyitz/aicm/example
Clone the repo
git clone --depth 1 https://github.com/ranyitz/aicm
Per session 31 This file is loaded in full into every session.
When invoked 31 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00031 $0.00031
Opus 5 $0.00015 $0.00015
Sonnet 5 $0.00006 $0.00006
Haiku 4.5 $0.00003 $0.00003

Measured 2d ago against content hash 7e833820f725, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

example 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 2d 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.

tests/fixtures/assets-dir-multitarget/rules/example.mdc · 6 lines

What it actually says

Example Rule

Reference the config file for configuration details.

Also check ../assets/data.json for data format.

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. 2d ago First seen · 6 lines · 31 tokens per session scan A 7e833820f725

Subscribe to this mod's changes

example is a cursor rule published in the GitHub repository ranyitz/aicm (36 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session, about $0.0002 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-30.