todo2code AGENTS.md

A set of repository rules for coding agents, stored in an AGENTS.md file. It uses policy-as-code, meaning project rules are written in files and checked by scripts.

In plain words
What is it for?
It helps manage implementation tickets, approvals, branches, worktrees, allowed files, governance checks, and completion checks.
Why use it?
It prevents agents from starting work without the required ticket, approval, files, and checks. It also limits edits to approved paths and keeps ticket work separated.

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/autogrammar/todo2code/agents-md
Clone the repo
git clone --depth 1 https://github.com/autogrammar/todo2code

Made for: Codex, OpenCode.

Per session 617 This file is loaded in full into every session.
When invoked 617 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.00617 $0.00617
Opus 5 $0.00309 $0.00309
Sonnet 5 $0.00123 $0.00123
Haiku 4.5 $0.00062 $0.00062

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

Security

Grade A, and why

todo2code 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 · 49 lines

What it actually says

AGENTS.md

This target repository follows wellmanifest/new-project policy-as-code.

Before any multi-step implementation, an agent must:

  1. Read .governance/manifest.json, TODO.md, project/TICKETS.md and the active ticket.
  2. Reuse an unfinished ticket whose workstream and scope match. A second active ticket is allowed only in a distinct workstream with no write-scope overlap. Otherwise run ./project/new-ticket.sh --title "..." --agent "..." --workstream "...".
  3. Complete the ticket README.md, owned ai-*.md, intent.json and TODO.md.
  4. Stop in WAIT_FOR_APPROVAL; do not change implementation files yet.
  5. After explicit approval, move to EDIT and stay inside intent.json allowedPaths.
  6. Never create or edit project/ticket-*/user-*.md; only its human owner or a trusted intake boundary may do so.
  7. Keep executable source/tests/scripts outside ticket directories.
  8. Run ./project/governance-check.sh plus the stack and Docker checks before reporting completion.
  9. Serialize ticket-ID allocation before branching, then use a separate branch/worktree per implementation ticket. Each diff must resolve to exactly one active ticket. Shared contract paths are edited only by the declared integration workstream; integrationTicket coordinates work but does not transfer path ownership.
  10. Only IN_PROGRESS reserves a workstream and write scope. BACKLOG, PLAN and BLOCKED retain evidence without blocking another implementation; transition back to IN_PROGRESS before changing source or tests.
  11. Treat GitHub review as trusted only when it targets the current HEAD and either a User login is in protected trusted-reviewers or a Bot login is in the separate protected trusted-validator-apps input. Never trust an arbitrary Bot review.
  12. Require merge approval evidence to bind repository, PR, current HEAD, active ticket and actor. The protected resolver creates that evidence outside the PR checkout; repository-authored evidence is untrusted.
  13. A signed attestation is trusted only after a protected verifier validates its signature, issuer, predicate type and subject bindings.
  14. Validator-agent examples use LLM_MODEL_VALIDATOR=openrouter/z-ai/glm-5.2; model findings stay advisory.
  15. Configure GitHub with delete_branch_on_merge=true. A merged ticket branch must disappear after merge. A PR closed without merge keeps its branch until the owner explicitly discards that unmerged work. When no PR is open, the only remote branch is the default branch.

Markdown approval is an audit note, not trusted merge authorization. Required merge approval comes from the repository's protected review, attestation and ruleset boundary.

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 · 49 lines · 617 tokens per session scan A c400cde1172a

Subscribe to this mod's changes

todo2code AGENTS.md is an instructions file published in the GitHub repository autogrammar/todo2code (0 stars, last pushed 6d ago), licensed Apache-2.0. It adds 617 tokens to every session, about $0.0031 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.

Related

Other instructions, from other repositories

plainweave AGENTS.md

AGENTS.md instructions for foundryside-dev/plainweave, covering filigree issue tracker, workflow, at session start, ...or claim a specific issue and do the work, commit, then.

foundryside-dev/plainweave · 2,773 tokens

plainweave CLAUDE.md

Claude Code instructions for foundryside-dev/plainweave, covering filigree issue tracker, workflow, at session start, ...or claim a specific issue and do the work, commit, then.

foundryside-dev/plainweave · 2,773 tokens

deepagents AGENTS.md

Instructions for langchain-ai/deepagents, covering global development guidelines for the deep agents monorepo, corridor security analysis, development workflow, suppressing ruff rules and pr conventions.

langchain-ai/deepagents · 2,268 tokens

autoharness AGENTS.md

Instructions for tigerless-labs/autoharness: This repo uses Open Knowledge — collaborative markdown via MCP. .open-knowledge/config.yml (with optional /.open-knowledge/config.yml; CLI/env may override) is the path contract: content.dir is the root for relative paths; content.include lists globs that add markdown…

tigerless-labs/autoharness · 2,201 tokens

cookiecutter-mlops-package AGENTS.md

Instructions for fmind/cookiecutter-mlops-package, covering agents.md, project overview, setup & core commands, definition of done and conventions & idioms.

fmind/cookiecutter-mlops-package · 1,296 tokens

python-cheatsheet copilot-instructions.md

Copilot instructions for labex-labs/python-cheatsheet, covering python cheatsheet - ai coding assistant instructions, project overview, architecture & key patterns, content structure and routing & layout system.

labex-labs/python-cheatsheet · 1,155 tokens