aidd AGENTS.md

An agent guide for a project that stores AI-development instructions in an `ai/` directory. It uses index files to describe folders and progressive discovery to load only the guidance relevant to a task.

In plain words
What is it for?
Use it before planning or running tasks in this repository, especially when navigating its AI rules, indexes, workflows, and domain-specific folders.
Why use it?
It helps an agent find the right instructions without reading unrelated project material, and requires the project vision to be read before work begins.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/paralleldrive/aidd/agents-md
Clone the repo
git clone --depth 1 https://github.com/paralleldrive/aidd

Made for: Codex, OpenCode.

Per session 464 This file is loaded in full into every session.
When invoked 464 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00464 $0.00464
Opus 5 $0.00232 $0.00232
Sonnet 5 $0.00093 $0.00093
Haiku 4.5 $0.00046 $0.00046

Measured yesterday against content hash c1f1aaa9fbb8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

AGENTS.md · 61 lines

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:

  1. Stop and identify the specific conflict
  2. Explain how the task conflicts with the stated vision
  3. 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.

Read the full file on GitHub · 61 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. yesterday First seen · 61 lines · 464 tokens per session scan A c1f1aaa9fbb8

Subscribe to this mod's changes

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.