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/pertamaxxx/agents/agents-mdgit clone --depth 1 https://github.com/pertamaxxx/agentsWrote 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/pertamaxxx/agents/agents-md)<a href="https://agentmods.dev/instructions/pertamaxxx/agents/agents-md"><img src="https://agentmods.dev/badge/instructions/pertamaxxx/agents/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.01717 | $0.01717 |
| Opus 5 | $0.00859 | $0.00859 |
| Sonnet 5 | $0.00343 | $0.00343 |
| Haiku 4.5 | $0.00172 | $0.00172 |
Grade A, and why
agents 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project overview
Cloudflare Agents SDK — a framework for building stateful AI agents on Cloudflare Workers. This is a monorepo containing the core SDK packages, examples, guides, sites, and documentation.
Repository structure
packages/ # Published npm packages (need changesets for changes)
agents/ # Core SDK (see packages/agents/AGENTS.md)
ai-chat/ # @cloudflare/ai-chat — higher-level AI chat agent
hono-agents/ # Hono framework integration
codemode/ # @cloudflare/codemode — experimental code generation
examples/ # Self-contained demo apps (see examples/AGENTS.md)
playground/ # Main showcase app — all SDK features in one UI (uses Kumo design system)
mcp/ # MCP server example
mcp-client/ # MCP client example
... # ~20 examples total
experimental/ # Work-in-progress experiments (not published, no stability guarantees)
site/ # Deployed websites
agents/ # agents.cloudflare.com (Astro)
ai-playground/ # Workers AI playground (React + Vite)
guides/ # In-depth pattern tutorials with narrative READMEs (see guides/AGENTS.md)
anthropic-patterns/
human-in-the-loop/
openai-sdk/ # Examples using @openai/agents SDK
basic/ chess-app/ handoffs/ human-in-the-loop/ ...
docs/ # Markdown docs for developers.cloudflare.com (see docs/AGENTS.md)
design/ # Architecture and design decision records (see design/AGENTS.md)
scripts/ # Repo-wide tooling (typecheck, export checks, update checks)
Nested AGENTS.md files
Some directories have their own AGENTS.md with deeper guidance:
| File | Scope |
|---|---|
packages/agents/AGENTS.md |
Core SDK internals — exports, source layout, build, testing, architecture |
examples/AGENTS.md |
Example conventions — required structure, consistency rules, known issues |
guides/AGENTS.md |
Guide conventions — how guides differ from examples, README expectations |
docs/AGENTS.md |
Writing user-facing docs — Diátaxis framework, upstream sync, style |
design/AGENTS.md |
Design records and RFCs — format, workflow, relationship to docs |
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 · 180 lines · 1,717 tokens per session scan A 90419b132ef2
agents AGENTS.md is an instructions file published in the GitHub repository pertamaxxx/agents (3 stars, last pushed 3d ago), licensed MIT. It adds 1,717 tokens to every session, about $0.0086 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
ai-agents-for-beginners AGENTS.md
Instructions for microsoft/ai-agents-for-beginners, covering agents.md, project overview, setup commands, prerequisites and initial setup.
turbo-flow CLAUDE.md
Claude Code instructions for marcuspat/turbo-flow, covering claude.md — turbo flow, what this repo is, key files and conventions.
Proma AGENTS.md
AGENTS.md instructions for proma-ai/Proma, covering proma 工程约定, 必须遵守, 常用命令, 开发 and 构建 / 类型检查 / 测试.
nextjs-skills CLAUDE.md
Instructions for mohamed-hossam1/nextjs-skills: All contribution rules — style, naming, file layout, verification — live in AGENTS.md. Read that first.
claude-code-safety-net CLAUDE.md
Instructions for waleedkhanbaloch/claude-code-safety-net, covering claude.md, project overview, commands, architecture and code style (typescript).
claude-code-safety-net AGENTS.md
Instructions for waleedkhanbaloch/claude-code-safety-net, covering agent guidelines, commands, pre-commit hooks, commit conventions and code style (typescript).