agent-requested-description-h2

A writing rule that lets an agent decide whether to include a supplied description, such as headings and their supporting text.

In plain words
What is it for?
It is for controlling which descriptions, headings, or section notes an agent includes in its output.
Why use it?
It helps the agent avoid adding every available description when only some of the content fits the task.

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/zackiles/cursor-config/agent-requested-description-h2
Clone the repo
git clone --depth 1 https://github.com/zackiles/cursor-config
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 52 The whole file, excluding the scripts and references it only reads on demand.
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.00016 $0.00052
Opus 5 $0.00008 $0.00026
Sonnet 5 $0.00003 $0.00010
Haiku 4.5 $0.00002 $0.00005

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

Security

Grade A, and why

agent-requested-description-h2 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.

test/mocks/passing-rules/agent-requested-description-h2.mdc · 11 lines

What it actually says

H2 Header

H2 header description

H3 Header

Some h3 sub-header section

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 · 11 lines · 16 tokens per session scan A bb7179cf9e0a

Subscribe to this mod's changes

agent-requested-description-h2 is a cursor rule published in the GitHub repository zackiles/cursor-config (17 stars, last pushed 1y ago), licensed MIT. It adds 16 tokens to every session and 52 once invoked, about $0.0001 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.