Borrowing it
Nothing to install: this file belongs to jhoblitt/rook-claude. 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/jhoblitt/rook-claude/main/AGENTS.mdgit clone --depth 1 https://github.com/jhoblitt/rook-claudeWrote 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/jhoblitt/rook-claude/agents-md)<a href="https://agentmods.dev/instructions/jhoblitt/rook-claude/agents-md"><img src="https://agentmods.dev/badge/instructions/jhoblitt/rook-claude/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.00802 | $0.00802 |
| Opus 5 | $0.00401 | $0.00401 |
| Sonnet 5 | $0.00160 | $0.00160 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
rook-claude 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 7d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Notes for agents and humans changing this repository. This repo is a Claude
Code plugin marketplace; the shipped product is plugins/rook-maintainer,
whose "code" is mostly instruction prose that steers a model. A prose defect
here is a real defect.
The contribution mechanics — Conventional Commits, never bumping the plugin
version by hand, and the checks CI runs — live in README.md under
"Development". This file does not restate them.
Skill workflows are documented in the README
Every skill that executes a procedure has a mermaid flowchart in
README.md under "Skill workflows", kept in sync with its SKILL.md.
A skill is a procedure if its SKILL.md has any of: numbered phases or
steps, a modes table, ordered gates, or agent fan-out. The test is
mechanical so the question is checkable rather than argued each time.
Changing a skill's phases, modes, gates, or fan-out is not complete until
its diagram matches. This clause is the point of the rule. Without it the
rule catches a missing diagram but not a stale one, and stale is the failure
that actually happens: when PR takeover moved out of rook-code-review into
its own skill, the skills table was updated and the diagram was left
asserting takeover was still a mode.
Adding a skill adds its diagram in the same PR. Removing one removes it.
Reference skills are exempt
A skill with no entry point, no ordered steps, and no output contract — one other skills consult rather than run — gets no workflow diagram. Diagramming a rules document invents a flow that does not exist and makes the README worse.
rook-conventions is the exempt case: its own text says references are read
by trigger and skipped otherwise, and that a report "lands in ITS OWN output
contract" — the caller's, not its. It has a precedence ladder where a
procedure would have an entry point.
An exemption claimed for a skill that in fact has phases or modes is a review blocker.
What an exempt skill owes instead
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.
- 7d ago First seen · 79 lines · 802 tokens per session scan A de0c7b8cdc0e
rook-claude AGENTS.md is an instructions file published in the GitHub repository jhoblitt/rook-claude (4 stars, last pushed 2d ago), licensed Apache-2.0. It adds 802 tokens to every session, about $0.0040 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.
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).
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.
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).
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.