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/toybz-creator/agent-guide/agents-mdgit clone --depth 1 https://github.com/toybz-creator/agent-guideWrote 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/toybz-creator/agent-guide/agents-md)<a href="https://agentmods.dev/instructions/toybz-creator/agent-guide/agents-md"><img src="https://agentmods.dev/badge/instructions/toybz-creator/agent-guide/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.03356 | $0.03356 |
| Opus 5 | $0.01678 | $0.01678 |
| Sonnet 5 | $0.00671 | $0.00671 |
| Haiku 4.5 | $0.00336 | $0.00336 |
Grade A, and why
agent-guide 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Purpose
This repository builds production-agent-guide, a reusable rule framework for AI coding agents. The project exists to make coding agents more production-minded, context-aware, safe, thorough, and useful across many downstream software projects.
Agents working here must treat this repository as both:
- a normal npm package with a CLI and published files
- the source of truth for instructions that other coding agents will follow
Because the package teaches agents how to behave, every change must be unusually clear, explicit, operational, and easy for a future agent to apply from a minimal user prompt.
Repository Map
README.md: public package overview, install instructions, activation snippet, setup flow, expected behavior, customization guidance, and publishing commands.instructions.md: base operating framework for coding agents. This is the primary behavior document, including theUpdate harnessand skill-command workflows.backend/backend-rules.md: production backend, API, data, reliability, observability, security, and operations rules.frontend/frontend-rules.md: production frontend, UI, accessibility, state, integration, performance, and testing rules.mobile/react-native-rules.md: production React Native and Expo architecture, UX, accessibility, native integration, performance, offline, security, testing, store, and release rules.computer-use/computer-use-agent-rules.md: browser automation, screenshots, desktop interaction, and UI verification rules.docs/: packaged library and framework references for supported stacks such as NextJS, NestJS, React, and TypeORM and so on.scripts/supply-chain-audit.mjs: built-in supply-chain audit scaffold copied into downstream projects.scripts/codebase-consistency-codemod.mjs: built-in consistency codemod scaffold copied into downstream projects.bin/pag.mjs: CLI entrypoint forinit,doctor,recommend,snippet, andhelp; it defines required downstreamharness/files, skill templates, and scaffold/doctor behavior.package.json: npm metadata, package files, binary mapping, scripts, and engine requirement.ignore.md: reference material that is not part of the active package contract unless the user explicitly asks to inspect it.
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 · 270 lines · 3,356 tokens per session scan A 853a64cb9541
agent-guide AGENTS.md is an instructions file published in the GitHub repository toybz-creator/agent-guide (5 stars, last pushed 1mo ago), licensed MIT. It adds 3,356 tokens to every session, about $0.0168 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
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.
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.
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).
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.