dnd_kit: Instructions file for Codex

AGENTS.md

dnd_kit AGENTS.md is an instructions file for Codex, OpenCode from iamv4g/dnd_kit. It costs 405 tokens per session, scanned A, original, MIT.

A set of instructions for developing dnd_kit, a software project for building drag-and-drop interfaces. It explains which documentation defines behavior and architecture, and how to validate changes in a repository containing multiple packages.

In plain words
What is it for?
It guides code changes, documentation work, planning across sessions, and package-level or repository-wide testing.
Why use it?
It helps the agent find the right project rules and run focused checks before making claims about a change. It also distinguishes read-only explanations from work that changes files.

Instructions file for CodexOpenCode

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

This is iamv4g/dnd_kit's own configuration. It tells Codex and OpenCode how to work on dnd_kit 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 dnd_kit configures →

Reuse

Borrowing it

Nothing to install: this file belongs to iamv4g/dnd_kit. 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/iamv4g/dnd_kit/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/iamv4g/dnd_kit

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 dnd_kit AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/iamv4g/dnd_kit/agents-md"><img src="https://agentmods.dev/badge/instructions/iamv4g/dnd_kit/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 405 This file is loaded in full into every session.
When invoked 405 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.00405 $0.00405
Opus 5.5 $0.00162 $0.00162
Sonnet 5.5 $0.00081 $0.00081
Haiku 4.5 $0.00040 $0.00040

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

Security

Grade A, and why

dnd_kit 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 · 41 lines

What it actually says

Agent Instructions

Project-specific authority:

  • README.md and docs/product/ define current product behavior.
  • docs/ARCHITECTURE.md and docs/decisions/ define package boundaries and lasting technical choices.
  • Use the focused package tests during development and the Melos validation lanes documented in README.md before claiming repository-wide proof.

Harness

Start with the requested outcome, then use the repository as the system of record. Read docs/WORKFLOW.md and only the product, design, plan, code, and validation material relevant to the task.

  • Answers, explanations, reviews, diagnoses, plans, and status reports are read-only. Inspect only what is needed and do not mutate repository or Harness state.
  • For a bounded change, use an ephemeral plan: inspect the affected behavior and existing proof, implement the change, and run behavior-appropriate validation. No control-plane operation is required.
  • Create or update one file under docs/plans/active/ when work spans sessions, needs coordination or an ordered sequence, has meaningful dependencies, or requires explicit recovery steps. Move it to docs/plans/completed/ only after validation.
  • Before editing, identify repository authority for each new externally observable policy. If materially different choices remain open, stop before edits; configurable defaults are not authority.
  • Also pause when product intent remains ambiguous, an action is difficult to recover, validation would be weakened, or the request does not authorize the needed action.
  • Claim completion only with relevant executable or observable evidence. Report the outcome, important changed surfaces, validation, and unresolved risks.

SQLite intake, story, trace, scoring, audit, and proposal commands are optional compatibility features. Use them only when explicitly requested or required by an external orchestrator.

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 · 41 lines · 405 tokens per session scan A 4310803320dd

Subscribe to this mod's changes

dnd_kit AGENTS.md is an instructions file published in the GitHub repository iamv4g/dnd_kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 405 tokens to every session, about $0.0016 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

dnd_kit AGENTS.md compared with instructions from other repositories

dnd_kit AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
dnd_kit AGENTS.mdiamv4g/dnd_kitInstructions file21mo agoMITA405Codex, 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