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.
npx agentmods add instructions/doncheli/don-cheli-sdd/agents-mdgit clone --depth 1 https://github.com/doncheli/don-cheli-sddWrote 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/instructions/doncheli/don-cheli-sdd/agents-md)<a href="https://agentmods.dev/instructions/doncheli/don-cheli-sdd/agents-md"><img src="https://agentmods.dev/badge/instructions/doncheli/don-cheli-sdd/agents-md.svg" alt="Measured on agentmods" 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.00233 | $0.00233 |
| Opus 5 | $0.00117 | $0.00117 |
| Sonnet 5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
don-cheli-sdd 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 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.
What it actually says
Don Cheli — Instructions for Codex and Other Agents
Cross-Tool Compatibility
This file is shared between:
- Claude Code (reads from
.claude/or root) - Google Antigravity (reads from
.agent/or root) - Cursor (reads from
.cursor/or root) - Codex (reads from root)
Tool-specific instructions are in their dedicated files:
CLAUDE.md→ Claude Code specificGEMINI.md→ Antigravity/Gemini specificprompt.md→ Amp/other agents
Identity
You are a development assistant operating under the Don Cheli framework (Specification-Driven Development).
Context
Read the files in .dc/ to understand the project state.
Rules
- All code requires tests (TDD)
- Root cause first, then the fix
- Evidence before assertions
- Output in the language configured in
.dc/config.yaml(default: Spanish)
Commands
Execute commands from comandos/ following the instructions in each file.
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.
- 2d ago First seen · 34 lines · 233 tokens per session scan A 0fe90a35b862
don-cheli-sdd AGENTS.md is an instructions file published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 25d ago), licensed Apache-2.0. It adds 233 tokens to every session, about $0.0012 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-03.
Other instructions, from other repositories
plan-build-run CLAUDE.md
Claude Code instructions for SienkLogic/plan-build-run, covering claude.md, what this is, critical rules, commands and architecture.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.