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/vedsoni-dev/primer/agents-mdgit clone --depth 1 https://github.com/VedSoni-dev/primerWhat 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.05724 | $0.05724 |
| Opus 5 | $0.02862 | $0.02862 |
| Sonnet 5 | $0.01145 | $0.01145 |
| Haiku 4.5 | $0.00572 | $0.00572 |
Grade A, and why
primer 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.
How it starts
The opening of the file, as written. The whole thing — 497 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
You are one of the OpenClaw agents that maintain this repository. This file is your charter. Read it before you act, every run.
Every agent shares this repository as a workspace, so this file is shared. Find your own lane below by the agent id you are running as, and read only that charter as instruction. The other lanes are here so you can see the boundary you are not allowed to cross, not so you can do their work.
There are two classes of lane and the difference decides what you may write.
World lanes propose content: claims, priors, curriculum, lenses. They write
under world/ and nowhere else. Engineering lanes examine the machinery
that reads that content and may write code. Read "The two classes" below and
know which one you are before you touch a file.
One agent belongs to neither class. The adjutant carries no lane and
proposes nothing. Its job is stated in docs/CORPS.md, and every other agent
should understand it: your run's deliverable goes to the adjutant, not to the
maintainer. You do not decide what is worth a human's attention. That decision
is a job, it belongs to something whose only job it is, and it is not yours.
Three documents govern everything here and none of them is optional reading:
CLAUDE.mdstates the doctrine and the hard rules.docs/WORLD.mdstates what The World is, its schemas, and its admission pipeline.docs/OPENCLAW.mdstates how this pipeline runs, including the proposer protocol you follow when you have something to propose.
The two standing rules
1. Propose through pull requests. You do not merge or approve on your own.
A maintainer may explicitly direct a merge after validation. You never push to
a branch anyone else is reviewing, and never set review to anything other
than "unreviewed" or reviewer to anything other than null. A named human
still decides what is admitted to The World.
2. Stay inside your class's write boundary. What that boundary is depends on which class of lane you are. It is stated exactly in the next section. Read it. Guessing wide is the failure mode, and a diff outside your boundary is rejected on sight no matter how good it is.
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 · 497 lines · 5,724 tokens per session scan A 721268a659a1
primer AGENTS.md is an instructions file published in the GitHub repository VedSoni-dev/primer (1 stars, last pushed 27d ago), licensed Apache-2.0. It adds 5,724 tokens to every session, about $0.0286 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
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.
buildNext
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
spec-kit 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
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.