ardur: Instructions file for Codex

AGENTS.md

ardur AGENTS.md is an instructions file for Codex, OpenCode from ArdurAI/ardur. It costs 6,115 tokens per session, scanned B, original, MIT.

The main instruction guide for coding agents in the ArdurAI/ardur repository. It explains the required startup steps, repository structure, commands, and trust boundaries.

In plain words
What is it for?
Use it when an agent starts work in the repository, especially to run the bootstrap script and read the generated project context.
Why use it?
It gives agents a consistent way to prepare before editing code and tells them which project information to trust.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents; mentions Claude Code; mentions AGENTS.md.

This is ArdurAI/ardur's own configuration. It tells Codex and OpenCode how to work on ardur itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ardur configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ArdurAI/ardur. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ArdurAI/ardur/dev/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/ArdurAI/ardur

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for ardur AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ardurai/ardur/agents-md/github.svg)](https://agentmods.dev/instructions/ardurai/ardur/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/ardurai/ardur/agents-md"><img src="https://agentmods.dev/badge/instructions/ardurai/ardur/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ardur AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/ardurai/ardur/agents-md"><img src="https://agentmods.dev/badge/instructions/ardurai/ardur/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6,115 This file is loaded in full into every session.
When invoked 6,115 The same file — it is already loaded in full.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.06115 $0.06115
Opus 5.5 $0.02446 $0.02446
Sonnet 5.5 $0.01223 $0.01223
Haiku 4.5 $0.00611 $0.00611

Measured 1mo ago against content hash 0d86b0b1882a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

ardur AGENTS.md scanned grade B with 1 finding 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 1mo 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo /tmp/ardur-seccomp-smoke --daemon-bin /tmp/ardur-kernelcaptured --shim-bin /tmp/ardur-exec-shim
AGENTS.md · 464 lines

How it starts

The opening of the file, as written. The whole thing — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ardur Agent Instructions

The canonical entry point for coding agents working in this repository. These instructions are mandatory. Human contributors should read CONTRIBUTING.md and docs/engineering-standards.md; this file restates the parts an agent gets wrong most often and adds the parts that only matter to agents.

0. First Action In Every New Session

Run the Conductor bootstrap before doing task-specific work:

./scripts/conductor-bootstrap.sh

Then read .context/ARDUR_CONTEXT.md. Its Generated Graph section is the authority for graph availability:

  • When the status is available, read .context/ardur-graph.md and use .context/ardur-graph.json as the machine-readable map of the repo.
  • When the status is unavailable, continue with the live source and workflow files listed in the context. Missing graph artifacts are optional in this path and are not a bootstrap failure.

If the bootstrap fails, stop and inspect the failure before editing files. A failed bootstrap usually means the local toolchain, branch state, or generated context is not trustworthy yet.

Repo truth hierarchy. Use live repo state over stale prose, in this order:

  1. git status, branch refs, and the actual files in this checkout.
  2. .github/workflows/ for the current CI surface.
  3. README.md, STATUS.md, docs/TESTING.md, docs/engineering-standards.md, docs/known-limitations.md, and docs/decisions/.
  4. Prior notes and generated .context/ files, after checking their timestamp.

If two sources conflict, cite the conflict and verify from the current tree. This repo has changed quickly around Python and Go CI; the live workflow files are the authority for what currently runs. That includes this file — if AGENTS.md disagrees with a workflow, the workflow is right and this file is a bug.

1. What Ardur Is, And What It Does Not Claim

Ardur governs AI-agent tool calls that pass through a configured adapter or proxy. It checks mission, resource, budget, and delegation constraints before that integration dispatches the call, then emits an issuer-signed, hash-linked receipt for the decision. The goal is to prove what your agents do, not just what they say.

Read the full file on GitHub · 464 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. 1mo ago First seen · 464 lines · 6,115 tokens per session scan B 0d86b0b1882a

Subscribe to this mod's changes

ardur AGENTS.md is an instructions file published in the GitHub repository ArdurAI/ardur (2 stars, last pushed 1mo ago), licensed MIT. It adds 6,115 tokens to every session, about $0.0245 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). 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

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens