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/me2resh/apexyard/agents-mdgit clone --depth 1 https://github.com/me2resh/apexyardWrote 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/me2resh/apexyard/agents-md)<a href="https://agentmods.dev/instructions/me2resh/apexyard/agents-md"><img src="https://agentmods.dev/badge/instructions/me2resh/apexyard/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.04477 | $0.04477 |
| Opus 5 | $0.02239 | $0.02239 |
| Sonnet 5 | $0.00895 | $0.00895 |
| Haiku 4.5 | $0.00448 | $0.00448 |
Grade A, and why
apexyard 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 2d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Entry point for AI coding agents (Cursor, Claude Code, Aider, Cline, pi, etc.) working inside this repository. This file now serves two audiences — read the section that matches what you're doing:
| You are… | Read |
|---|---|
An agent operating inside an apexyard ops fork on behalf of an adopter — governing a portfolio, working a ticket, opening a PR — and you don't auto-load CLAUDE.md (this is the normal case for pi and most non-Claude-Code harnesses) |
"Operator governance bridge" below, first |
| An agent extending apexyard's own source (hooks, skills, rules, agents) — i.e. contributing to the framework itself | "Framework repo orientation" further down |
| Claude Code | Neither — CLAUDE.md is auto-loaded at session start and already covers the governance bridge in full; skim "Framework repo orientation" only if you're also touching the framework's own internals |
Why two audiences in one file: CLAUDE.md is the framework-level instruction set Claude Code auto-loads inside an ops fork. Harnesses that don't recognise CLAUDE.md — pi chief among them — auto-load AGENTS.md instead (from cwd, or ~/.pi/agent/). Before this section existed, a pi user landing in an apexyard ops fork got only the framework-contributor orientation below — useful if you're hacking on apexyard's hooks, useless if you're trying to run the SDLC it governs. This section closes that gap.
Operator governance bridge (pi and other non-Claude-Code harnesses)
Advisory by default — mechanical enforcement is opt-in for pi. Everything below is delivered as instructions; Claude Code's governance additionally runs as shell hooks (
.claude/hooks/*.sh, wired via.claude/settings.json) that mechanically block bad commands — the two-marker merge gate, the ticket-first edit block, the secrets scanner, the AgDR-required check. Those hooks fire on Claude Code'sPreToolUse/PostToolUseevents. pi doesn't expose that event surface directly, but as of me2resh/apexyard#815 a dispatcher extension (harness-adapters/pi/) shells out to the SAME unmodified hooks via pi's owntool_callevent — install it (harness-adapters/pi/README.md) and pi gets real mechanical enforcement, not just prose. Without that extension installed, nothing in this file will stop a tool call for you — follow these rules because they're the governance model apexyard is built on, not because a hook will catch you if you don't. Seedocs/harnesses/pi.mdfor the current mechanically-enforced-vs-advisory-only breakdown.
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.
- 2d ago First seen · 185 lines · 4,477 tokens per session scan A 9dafedc66750
apexyard AGENTS.md is an instructions file published in the GitHub repository me2resh/apexyard (499 stars, last pushed today), licensed MIT. It adds 4,477 tokens to every session, about $0.0224 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-09-03.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).