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/aaddrick/attention-control/claude-mdgit clone --depth 1 https://github.com/aaddrick/attention-controlWrote 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/aaddrick/attention-control/claude-md)<a href="https://agentmods.dev/instructions/aaddrick/attention-control/claude-md"><img src="https://agentmods.dev/badge/instructions/aaddrick/attention-control/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.02266 | $0.02266 |
| Opus 5 | $0.01133 | $0.01133 |
| Sonnet 5 | $0.00453 | $0.00453 |
| Haiku 4.5 | $0.00227 | $0.00227 |
Grade A, and why
attention-control 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.
This is a copy
98% identical to attention-control AGENTS.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in this repository
This repository ships one output style to seven coding agents. One file is canonical. Everything else is generated from it or checked against it.
Read this before you edit anything here.
The one rule that breaks the build
Edit output-styles/attention-control.md.
Never edit a generated file.
These files are generated. Each carries a "Do not edit this file" marker:
| Generated file | Built from |
|---|---|
skills/attention-control/SKILL.md |
the canonical style |
.cursor/skills/attention-control/SKILL.md |
the canonical style |
.cursor/rules/attention-control.mdc |
the canonical style |
the snippet section of INSTALL.md |
the canonical style |
AGENTS.md |
CLAUDE.md |
AGENTS.md and CLAUDE.md say the same thing. Edit CLAUDE.md and run the
generator; the mirror follows.
Which file your tool reads
| Tool | Reads | For |
|---|---|---|
| Claude Code | CLAUDE.md |
these standards |
| Cursor | AGENTS.md and CLAUDE.md, both automatic |
these standards |
| Gemini CLI | AGENTS.md, then GEMINI.md |
these standards, then the style |
| Any other agent-instruction harness | AGENTS.md |
these standards |
GEMINI.md is not a repository guide. gemini-extension.json names it as the
extension's context file, so it is what a Gemini CLI user gets when they
install this style. Leave it as the style.
.gemini/settings.json adds AGENTS.md to the context list, so a Gemini agent
working here reads the standards and the style. It changes nothing for anyone
who installs the extension.
After any edit to a source file, run:
python3 scripts/sync_style.py
CI fails when a copy drifts. scripts/sync_style.py --check is the gate.
Write in the style you are editing
This repository uses its own output style. Apply it to your responses and to the prose you write into these files.
- Lead with the next action. A command, a path, or a snippet goes first.
- Do the work you own. Never hand back a step you can finish yourself.
- Give the runnable thing. "Run the migration script" is a label. The path or the snippet is an action.
- Never invent a specific. A version, a date, a flag, or a line number you cannot check is a fabrication, whatever tone you write it in.
- State errors flat: location, cause, fix.
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 · 231 lines · 2,266 tokens per session scan A 7e1dfca427d6
attention-control CLAUDE.md is an instructions file published in the GitHub repository aaddrick/attention-control (102 stars, last pushed 25d ago), licensed MIT. It adds 2,266 tokens to every session, about $0.0113 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to attention-control AGENTS.md, differing in 2 lines, and is treated as a copy.
Other instructions, from other repositories
codemap AGENTS.md
Instructions for beadnall/codemap, covering codemap, if you are claude, if you are grok build, if you are another agent and the short version.
codemap copilot-instructions.md
Instructions for beadnall/codemap: This repository holds a skill for turning a codebase into an explorable isometric diagram. The full instructions are in SKILL.md — read that file and follow it when asked to map, diagram or visually explain how a system fits together.
neurodock CLAUDE.md
Claude Code instructions for tlennon-ie/neurodock, covering working in this repository (ai-agent instructions) and ci gotchas.
penpot-mcp copilot-instructions.md
Copilot instructions for ar27111994/penpot-mcp, covering workspace context, project guidelines, repository purpose, source layout and authoring style.
starwind-ui AGENTS.md
Instructions for starwind-ui/starwind-ui, covering agents.md, project shape, useful commands and contribution conventions.
OpenGUI CLAUDE.md
Claude Code instructions for Core-Mate/OpenGUI, covering opengui release - repository guide for claude code / codex, 1. repository positioning, 2. default working rules, 3. high-level architecture and 4. directory map.