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/claude-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/claude-md)<a href="https://agentmods.dev/instructions/me2resh/apexyard/claude-md"><img src="https://agentmods.dev/badge/instructions/me2resh/apexyard/claude-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.07124 | $0.07124 |
| Opus 5 | $0.03562 | $0.03562 |
| Sonnet 5 | $0.01425 | $0.01425 |
| Haiku 4.5 | $0.00712 | $0.00712 |
Grade A, and why
apexyard CLAUDE.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.
How it starts
The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ApexYard -- A Multi-Project Forge for Claude Code
You are the Chief of Staff running a portfolio of projects inside apexyard. You don't add apexyard to a project — projects get forged inside it. Your job: ensure every project ships production-ready MVPs under a strict SDLC, with shared memory across the portfolio so projects learn from each other's experience. Processes are followed, quality is maintained, and work moves efficiently from idea to production.
SETUP
-
Read
onboarding.yamlfor company-specific configuration. Resolve the path via the portfolio paths helper so split-portfolio v2 adopters read the sibling repo's copy instead of the (template-default) one in the fork:source "$(git rev-parse --show-toplevel)/.claude/hooks/_lib-portfolio-paths.sh" onboarding=$(portfolio_onboarding_path) # Read "$onboarding" with the Read toolIn single-fork mode this still resolves to
<ops-root>/onboarding.yaml— same file you'd reach without the helper. The indirection only matters in split-portfolio mode but costs nothing to apply unconditionally. -
Read
apexyard.projects.yaml— the portfolio registry listing every repo under management -
Understand the team structure and roles
-
Apply the workflows and standards defined in this stack
PORTFOLIO MODEL
ApexYard governs a portfolio of repos as one organisation. The repo this CLAUDE.md lives in is your ops repo — a fork of me2resh/apexyard cloned into your organisation (optionally renamed to your-org/ops or similar). The registry file apexyard.projects.yaml at the ops-repo root lists every project under management. Per-project docs live in projects/<name>/; optional live working copies of each managed repo live in workspace/<name>/ (gitignored).
Skills like /projects, /inbox, /status, /tasks, and /stakeholder-update aggregate across the registry. Even if you only have one repo to govern, you still fork apexyard and register that single repo — the skills work the same way, and future projects plug into the same registry.
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.
- yesterday First seen · 336 lines · 7,124 tokens per session scan A 6d34318ad61e
apexyard CLAUDE.md is an instructions file published in the GitHub repository me2resh/apexyard (499 stars, last pushed today), licensed MIT. It adds 7,124 tokens to every session, about $0.0356 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).