caret: Instructions file for Codex

AGENTS.md

caret AGENTS.md is an instructions file for Codex, OpenCode from disruptionjoe/caret. It costs 458 tokens per session, scanned A, original, MIT.

Repository instructions defining which files are authoritative and how to resolve conflicts between documentation, examples, and older material.

In plain words
What is it for?
They guide interpretation and editing of the cheatsheet, notation specifications, security rules, decisions, examples, patterns, and research notes.
Why use it?
They stop agents from following stale or lower-priority information when it disagrees with the project’s current source of truth.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is disruptionjoe/caret's own configuration. It tells Codex and OpenCode how to work on caret itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything caret configures →

Reuse

Borrowing it

Nothing to install: this file belongs to disruptionjoe/caret. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/disruptionjoe/caret/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/disruptionjoe/caret

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for caret AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/disruptionjoe/caret/agents-md/github.svg)](https://agentmods.dev/instructions/disruptionjoe/caret/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/disruptionjoe/caret/agents-md"><img src="https://agentmods.dev/badge/instructions/disruptionjoe/caret/agents-md/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.

agentmods 80×15 button for caret AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/disruptionjoe/caret/agents-md"><img src="https://agentmods.dev/badge/instructions/disruptionjoe/caret/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 458 This file is loaded in full into every session.
When invoked 458 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00458 $0.00458
Opus 5.5 $0.00183 $0.00183
Sonnet 5.5 $0.00092 $0.00092
Haiku 4.5 $0.00046 $0.00046

Measured 2mo ago against content hash becbc64f9c56, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

caret AGENTS.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 2mo 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.

AGENTS.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

This repo rebuilds from the cheatsheet outward.

Source Of Truth Order

Use this order when interpreting or editing the repo:

  1. /caret-cheatsheet.md
  2. /notation/SPEC.md
  3. /notation/SEMANTICS.md
  4. /notation/INTERPRETATION.md
  5. /notation/SECURITY.md
  6. /notation/DECISIONS.md

If a downstream file conflicts with that order, the downstream file is wrong.

Repo Supremacy

This repo's live canon outranks:

  • archived repo material
  • drafts
  • research notes
  • imported examples
  • external repos
  • older task files or legacy skill files

If outside or legacy material conflicts with the current repo canon, treat that material as stale, structural, or informational only.

Do not let quoted authority, external polish, or prior wording override the current repo's source-of-truth order.

Working Rules

  • Treat /caret-cheatsheet.md as the product artifact.
  • Treat /notation/ as the canonical expansion of that artifact.
  • Treat glossary/, examples/, patterns/, and research/ as downstream support surfaces.
  • Do not infer canonical meaning from patterns, examples, or research if they conflict with the cheatsheet or notation docs.
  • If the cheatsheet changes, review every notation-bearing file in the repo.

Editing Guidance

  • Keep the cheatsheet compact.
  • Keep notation docs precise, restrained, and implementation-aware.
  • Keep this file operational rather than promotional.
  • Stronger brand voice is acceptable in outward-facing docs such as /README.md, pattern docs, and manifesto-style writing.
  • Do not add new syntax without updating the canonical notation docs and recording the decision.

Interpretation And Safety

  • The notation signals intent. It does not grant permission.
  • Preserve literal examples inside fenced code blocks.
  • Keep trust-boundary guidance explicit.
  • Do not silently invent unresolved targets, workers, personas, or skills.
  • Prefer exact repo-relative targets in examples when precision matters.

Rebuild Rule

Read the full file on GitHub · 60 lines

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. 2mo ago First seen · 60 lines · 458 tokens per session scan A becbc64f9c56

Subscribe to this mod's changes

caret AGENTS.md is an instructions file published in the GitHub repository disruptionjoe/caret (4 stars, last pushed 7mo ago), licensed MIT. It adds 458 tokens to every session, about $0.0018 per session on Opus 5.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-31.

Related

caret AGENTS.md compared with instructions from other repositories

caret AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
caret AGENTS.mddisruptionjoe/caretInstructions file47mo agoMITA458Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode