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/paralleldrive/aidd/agents-mdgit clone --depth 1 https://github.com/paralleldrive/aiddWhat 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.00464 | $0.00464 |
| Opus 5 | $0.00232 | $0.00232 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
aidd 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guidelines
This project uses AI-assisted development with structured guidance in the ai/ directory.
Directory Structure
Agents should examine the ai/* directory listings to understand the available commands, rules, and workflows.
Index Files
Each folder in the ai/ directory contains an index.md file that describes the purpose and contents of that folder. Agents can read these index files to learn the function of files in each folder without needing to read every file.
Important: The ai/**/index.md files are auto-generated from frontmatter. Do not create or edit these files manually—they will be overwritten by the pre-commit hook.
Progressive Discovery
Agents should only consume the root index until they need subfolder contents. For example:
- If the project is Python, there is no need to read JavaScript-specific folders
- If working on backend logic, frontend UI folders can be skipped
- Only drill into subfolders when the task requires that specific domain knowledge
This approach minimizes context consumption and keeps agent responses focused.
Vision Document Requirement
Before creating or running any task, agents must first read the vision document (vision.md) in the project root.
The vision document serves as the source of truth for:
- Project goals and objectives
- Key constraints and non-negotiables
- Architectural decisions and rationale
- User experience principles
- Success criteria
Conflict Resolution
If any conflicts are detected between a requested task and the vision document, agents must:
- Stop and identify the specific conflict
- Explain how the task conflicts with the stated vision
- Ask the user to clarify how to resolve the conflict before proceeding
Never proceed with a task that contradicts the vision without explicit user approval.
Skills
import @skills/index.md import @aidd-custom/skills/index.md
Custom Skills and Configuration
Project-specific customization lives in aidd-custom/. Before starting work,
read aidd-custom/index.md to discover available project-specific skills,
and read aidd-custom/config.yml to load configuration into context.
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 · 61 lines · 464 tokens per session scan A c1f1aaa9fbb8
aidd AGENTS.md is an instructions file published in the GitHub repository paralleldrive/aidd (379 stars, last pushed 2mo ago), licensed MIT. It adds 464 tokens to every session, about $0.0023 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-30.
Other instructions, from other repositories
mcp-toolbox GEMINI.md
Gemini CLI instructions for googleapis/mcp-toolbox, covering mcp toolbox context & style guide, project overview, tech stack, key directories and development workflow.
open-agents AGENTS.md
AGENTS.md instructions for vercel-labs/open-agents, covering agents.md, quick links, authentication, database & migrations and environment isolation.
relay AGENTS.md
Instructions for AgentWorkforce/relay, covering git workflow rules, never push directly to main, correct workflow, ... do work .. and stop here - let user merge.
axonhub AGENTS.md
AGENTS.md instructions for looplj/axonhub, covering agents.md, global rules, configuration, project overview and technology stack.
axonhub CLAUDE.md
Claude Code instructions for looplj/axonhub: @AGENTS.md read and follow its instructions.
neeko AGENTS.md
Instructions for tincopper/neeko, covering neeko — repository guidelines, 项目概览, 目录结构, 前端(feature-based 架构) and 后端(domain-driven 模块化架构).