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/soliestre/idd/agents-mdgit clone --depth 1 https://github.com/SoliEstre/iddWhat 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 | $0.00590 | $0.00590 |
| Opus 5 | $0.00295 | $0.00295 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
idd 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Public repository rules
This repository is the public surface of the IDD project. Keep every change safe to publish.
Read before changing files
- Read
README.md,docs/status.md, and the document you will change. - Use English for the main document. Add or update the matching Korean document when the meaning changes.
- Treat
ai/idd-spec.mdas a dense expert and machine-readable projection, not as permission to invent missing decisions. - Treat
skills/idd/SKILL.mdas the canonical agent workflow. Keep Codex, Claude Code, Gemini CLI, and human documentation aligned with it.
Public boundary
- Never add secrets, personal data, private links, internal reports, agent transcripts, or local machine details.
- Separate verified facts, inferences, proposals, and open questions.
- Do not claim that IDD improves speed, quality, or safety until a public evidence record supports the claim.
- Do not present either
DefendorDistillas the settled final word in a canonical three-part name. - This repository is licensed under the MIT License. Preserve
LICENSE, its copyright notice, and the distinction between project-owned and separately identified third-party material.
Writing level
- The introduction site uses L1.1.1: everyday language, full sentences, and an explanation before a technical term.
- General documents use L1.1.1 through L1.2.2: plain language with a small amount of defined terminology.
ai/uses L5.5.5: compact expert terminology, explicit invariants, formal states, provenance, and failure conditions.
Method rules
- Use one isolated probe for one core uncertainty.
- Record the intended question and safety limits before implementation.
- Do not promote a probe without a human decision and a matching test, contract, or evaluation.
- Require a verifier that is independent from the implementation attempt before calling a change shippable.
- Prefer a reproducible local check for every enforced gate.
- Keep the skill agent-neutral. Put runtime-specific metadata in
.codex-plugin/,.claude-plugin/,gemini-extension.json, orskills/idd/agents/rather than forking the workflow.
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.
- yesterday First seen · 43 lines · 590 tokens per session scan A 20d472c17d29
idd AGENTS.md is an instructions file published in the GitHub repository SoliEstre/idd (1 stars, last pushed 24d ago), licensed MIT. It adds 590 tokens to every session, about $0.0030 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-31.
Other instructions, from other repositories
abap_wiki AGENTS.md
Instructions for Gixsy95/abap_wiki, covering agents.md - abapwiki operating contract, 1. identity and mission, 2. language, 3. architecture: the two planes and 4. inviolable rules.
agentfootprint AGENTS.md
Instructions for footprintjs/agentfootprint, covering agentfootprint — agent instructions (openai codex), core thesis, the mental model — three slots, six flavors, mock-first development (recommended workflow) and public api.
awaithumans-human-in-the-loop-ai-agents CLAUDE.md
Instructions for awaithumans/awaithumans-human-in-the-loop-ai-agents, covering awaithumans — codebase guide, what this project is, architecture overview, monorepo structure and package dependency rules.
agentfootprint CLAUDE.md
Instructions for footprintjs/agentfootprint, covering agentfootprint — feature-work map, before you design it: it may already exist, module map, core state & flow and extension points.
agentic-delivery-playbook AGENTS.md
Instructions for arcayne/agentic-delivery-playbook: Use adapters/codex/AGENTS.md as the repository operating instructions.
hive-orchestrator AGENTS.md
Instructions for intertwine/hive-orchestrator, covering agents, first steps, working rules, skills and fast path.