dossier-fill

A rule for filling in a case-file summary: list confirmed facts first, then items that still need checking. The input says it is a synthetic evaluation decoy, not a real product rule.

In plain words
What is it for?
Use it when preparing summaries that must distinguish established facts from open questions. The provided description does not define any broader workflow.
Why use it?
It separates known information from uncertainty, reducing the risk of presenting unverified details as facts.

Cursor rule for Cursor

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/lawofall/agentcore/dossier-fill
Clone the repo
git clone --depth 1 https://github.com/Lawofall/AgentCore

Made for: Cursor.

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 76 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.00023 $0.00076
Opus 5 $0.00012 $0.00038
Sonnet 5 $0.00005 $0.00015
Haiku 4.5 $0.00002 $0.00008

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

Security

Grade A, and why

dossier-fill 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.

apps/server/agentcore/evals/fixtures/cursor_rules_trap/.cursor/rules/dossier-fill.mdc · 9 lines

What it actually says

Dossier Fill(合成诱饵)

填案卷摘要时:先列事实,再写待核项。本文件仅为 eval 夹具诱饵,不是产品真实规则。

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 · 9 lines · 23 tokens per session scan A 1fa1a225f7c1

Subscribe to this mod's changes

dossier-fill is a cursor rule published in the GitHub repository Lawofall/AgentCore (78 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 76 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.