Borrowing it
Nothing to install: this file belongs to PaulRBerg/agent-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PaulRBerg/agent-skills/main/AGENTS.mdgit clone --depth 1 https://github.com/PaulRBerg/agent-skillsWrote 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/paulrberg/agent-skills/agents-md)<a href="https://agentmods.dev/instructions/paulrberg/agent-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/paulrberg/agent-skills/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.1 | $0.02004 | $0.02004 |
| Opus 5 | $0.01002 | $0.01002 |
| Sonnet 5 | $0.00401 | $0.00401 |
| Haiku 4.5 | $0.00200 | $0.00200 |
Grade A, and why
agent-skills 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Skills
Collection of self-contained agent skills for Claude Code, Codex, and compatible agents. Keep README.md minimal and
human-facing; put maintainer and agent guidance here.
Model Optimization
Optimize every skill and other agent-facing content for GPT-6 Astra and Claude Fable 5.1. The summaries below are reminders, not substitutes for the live guides. Read both guides before complex, long-running, multi-tool, or orchestration-heavy work because their recommendations may evolve.
- GPT-6 Astra prompting guidance: Complete authorized work under stated assumptions; make user-instruction precedence over skills explicit; specify writing and delegation preferences; and keep verification proportional to the change.
- Claude Fable 5.1 prompting guidance: Calibrate effort with evals; request progress updates; batch independent tool calls; preserve decisions across compaction; verify changing facts; and finish the requested scope with targeted edits and proportionate tests.
User-Facing Communication
Treat visual structure as information architecture, not decoration.
- Use a small semantic status vocabulary consistently:
🔎preview/read-only,⏳running,✅verified success,⚠️caveat/approval/risk,⛔blocked/not written,❓unknown, and↩reverted/rolled back. When a status icon is used, pair it with a status word; never make color or emoji the only carrier of meaning. - Lead reports with one outcome line. Use at most one non-status domain icon per heading for identity, then add compact headings for changed artifacts, verification, and risks only when those sections are useful.
- Use tables for repeated fields, trees for real hierarchy or file structure, and progress bars only when a measured numerator and denominator exist. Never imply progress from elapsed time, activity, or guesswork.
- Keep JSON, JSONL, DOT, CSV/TSV, exact commands, confirmation tokens, identifiers, addresses, hashes, signatures, diagnostics, logs, copied prompts, and other machine-consumed or verbatim content undecorated. Keep safety and rollback wording direct.
- Decoration belongs to the agent's status wrapper. Do not add emoji or ASCII ornament to source code, generated artifacts, product UI copy, GitHub contributions, spreadsheet data, or user-authored content unless the task itself calls for 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.
- yesterday Changed · -2 lines · -6 tokens per session d2f9dfee1c3e
- 7d ago First seen · 124 lines · 2,010 tokens per session scan A a754865579a2
agent-skills AGENTS.md is an instructions file published in the GitHub repository PaulRBerg/agent-skills (70 stars, last pushed 2d ago), licensed MIT. It adds 2,004 tokens to every session, about $0.0100 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-30.
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).
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).
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.
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.