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.
git clone --depth 1 https://github.com/FrigateCaptain/ElucidatingYourLLMWrote 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/rules/frigatecaptain/elucidatingyourllm/control-files-archive)<a href="https://agentmods.dev/rules/frigatecaptain/elucidatingyourllm/control-files-archive"><img src="https://agentmods.dev/badge/rules/frigatecaptain/elucidatingyourllm/control-files-archive/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.
<a href="https://agentmods.dev/rules/frigatecaptain/elucidatingyourllm/control-files-archive"><img src="https://agentmods.dev/badge/rules/frigatecaptain/elucidatingyourllm/control-files-archive.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00031 | $0.00232 |
| Opus 5 | $0.00015 | $0.00116 |
| Sonnet 5 | $0.00006 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
control-files-archive 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.
What it actually says
A control file is one used to make a decision or to diagnose: a map of links, a diagram, a registry, a plan, a checklist. A historical incident record, a change journal, and a history of blocks are not control files in this sense: they are not archived and not rewritten after the fact to match a new state.
When the state described in a control file has changed, or when it is found that the file describes a state that no longer exists:
- Rewrite the live version to match the actual state.
- Move the outdated version into
archive/in the same folder. Do not leave an outdated copy next to the live file in the shared folder. - Put a link to the live file in the archived copy. Put a link to the archived copy in the live file.
The trigger is a state change or a discovered mismatch, not "sometime at the next review."
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 · 15 lines · 31 tokens per session scan A dc2f2bd14cf4
control-files-archive is a cursor rule published in the GitHub repository FrigateCaptain/ElucidatingYourLLM (14 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 232 once invoked, 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-09-05.
Other cursor rules, from other repositories
monorepo-and-tooling
Rules for projects that may use a monorepo, a single repository containing multiple applications or shared packages. They also define Taskfile commands and how to keep environment settings outside the code.
folder-structure
A prescribed folder layout for React applications that use MobX, a library for managing shared application state. It separates components, pages, stores, hooks, utilities, and static assets.
state-transition-rule
A rule describing a request status flow from pending to approved and then to item creation. It is written in Chinese.
history-and-next-task-rules
A response-formatting guide that requires an assistant to summarize the work, show the source tree, and identify the next task.
build-notes-guidelines
A process for creating and updating a build-note file for each task group. The notes record plans, progress, decisions, and changes over time.
kotlin-springboot-rules
A set of coding rules for Kotlin applications built with Spring Boot, a Java-based framework for web services. It covers project layout, naming, Kotlin style, and common design patterns.