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/brmbh/wordpress/agents-mdgit clone --depth 1 https://github.com/brmbh/wordpressWhat 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.01844 | $0.01844 |
| Opus 5 | $0.00922 | $0.00922 |
| Sonnet 5 | $0.00369 | $0.00369 |
| Haiku 4.5 | $0.00184 | $0.00184 |
Grade A, and why
wordpress 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.
The source is not reproduced here
Licensed GPL-2.0
The repository is licensed GPL-2.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 133 lines · 1,844 tokens per session scan A 1d2e5bea3be7
wordpress AGENTS.md is an instructions file published in the GitHub repository brmbh/wordpress (5 stars, last pushed 19d ago), licensed GPL-2.0. It adds 1,844 tokens to every session, about $0.0092 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
gentelella copilot-instructions.md
Instructions for ColorlibHQ/gentelella, covering github copilot instructions — gentelella v4, hard rules, file layout, anti-patterns and commands.
maroto AGENTS.md
Instructions for johnfercher/maroto, covering agent instructions, skills, definition of done, contributing commands and tool dependencies.
base AGENTS.md
Instructions for basefoundry/base, covering ai agent guidance, working agreement, github workflow, repository release contract and validation.
base copilot-instructions.md
Instructions for basefoundry/base: Use AGENTS.md as the canonical workflow guidance for Base. These instructions exist to point Copilot at the same repository-owned rules used by other coding agents; they do not replace AGENTS.md, CONTRIBUTING.md, STANDARDS.md, or the .ai-context/ orientation files.
lazy-starter-kit CLAUDE.md
Instructions for Heoooooon/lazy-starter-kit: Follow the safety rules in AGENTS.md. In particular, never execute recursive rm directly; use lazy-safe-rm for a strict descendant of the current Git workspace.
paperclip-plugin-company-wizard CLAUDE.md
Instructions for Yesterday-AI/paperclip-plugin-company-wizard, covering claude.md, what this is, commands, architecture and source layout.