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/ardurai/ardur-agent/agents-mdgit clone --depth 1 https://github.com/ArdurAI/ardur-agentWrote 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.
[](https://agentmods.dev/instructions/ardurai/ardur-agent/agents-md)<a href="https://agentmods.dev/instructions/ardurai/ardur-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/ardurai/ardur-agent/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01210 | $0.01210 |
| Opus 5 | $0.00605 | $0.00605 |
| Sonnet 5 | $0.00242 | $0.00242 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
ardur-agent 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 3d 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.
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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ardur Agent Session Instructions
These instructions apply to every LLM, coding agent, and human-assisted agent session that works in this repository.
Mandatory Bootstrap
Before planning, editing, testing, or creating a handoff, run:
python3 scripts/agent_bootstrap.py
Use --json only when a tool needs machine-readable output:
python3 scripts/agent_bootstrap.py --json
The bootstrap is read-only. It reports current Linear status, project progress,
Git/worktree state, provider and memory posture, unowned parallel:ready
candidates, the Plan Corpus verification backlog, and the required non-
interference rules for parallel sessions.
If the generic Linear connector shows a workspace or team other than
ardur-agent / ARD, do not claim that work. The bootstrap uses the
Keychain-backed helper at architect/tools/linear_graphql.py and must be the
source for ARD work discovery.
Source Hierarchy
- Linear
ARDis the internal source of truth for work scope, active state, priority, acceptance criteria, progress, blockers, and verification evidence. - EXTENDED drive is the primary file/evidence source for plans, journals, audits, local branches, and implementation evidence.
- GitHub
ArdurAI/ardur-agentis the verified public code surface for PRs, CI, releases, and public collaboration. - Notion is a knowledge projection, useful for durable explanation and navigation, but it is not the authority for whether work is complete.
Session Ownership Rule
Before code edits, a session must claim one unowned parallel:ready Linear
issue. After claiming it, update Linear to parallel:owned or In Progress and
record:
- one Linear issue,
- one branch or isolated worktree,
- one EXTENDED-drive session journal,
- one explicit file/module scope.
Never claim issues from a non-ARD workspace while working in this repository. Wrong-workspace Linear access is a blocker, not a reason to switch projects.
Preferred branch format:
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.
- 3d ago First seen · 143 lines · 1,210 tokens per session scan A ee1cddc86322
ardur-agent AGENTS.md is an instructions file published in the GitHub repository ArdurAI/ardur-agent (2 stars, last pushed 7d ago), licensed Apache-2.0. It adds 1,210 tokens to every session, about $0.0060 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
rovai-ai AGENTS.md
AGENTS.md instructions for murray17/rovai-ai, covering agents.md, project documentation and frontend design.
jockey CLAUDE.md
Instructions for recailai/jockey, covering claude.md, commands, development, architecture and file layout.
acp-forge AGENTS.md
Instructions for ky2renzzz/acp-forge, covering acp forge — agent instructions, project overview, architecture, conventions and build & test.
jockey AGENTS.md
Instructions for recailai/jockey, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
research-os AGENTS.md
Instructions for lxinfei5/research-os, covering researchos — constitution, §0 what this is, §1 directory discipline, §2 half-life (innovation 1) — memory design and §3 behavior pillars (innovations 2–5).