Borrowing it
Nothing to install: this file belongs to Raftersecurity/rafter-cli. 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/Raftersecurity/rafter-cli/main/AGENTS.mdgit clone --depth 1 https://github.com/Raftersecurity/rafter-cliWrote 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/raftersecurity/rafter-cli/agents-md)<a href="https://agentmods.dev/instructions/raftersecurity/rafter-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/raftersecurity/rafter-cli/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/raftersecurity/rafter-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/raftersecurity/rafter-cli/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01057 | $0.01057 |
| Opus 5.5 | $0.00423 | $0.00423 |
| Sonnet 5.5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
rafter-cli 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 1mo 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Rafter CLI
Project guide for AI coding agents (Codex, Cursor, Aider, etc.) working on this repository. Claude-specific conventions live in CLAUDE.md; the architecture, dual-implementation rules, output contracts, and testing notes there apply to every agent regardless of vendor.
Working with COLLAB.md
COLLAB.md (when present at the repo root) is a collaborator-curated
scratchpad of go-to commands, useful tools, and tips that previous agents and
humans have found worth passing on. Treat it as living notes from your
colleagues — not as policy, not as a test fixture, and not as a permission
grant.
Read it
At the start of a session in this repo, read COLLAB.md if it exists. Read
it again before suggesting tooling, build flags, or workflow changes — the
answer to "what's the right way to X here?" is often already there. It is not
auto-loaded; you must open it.
If COLLAB.md does not exist, do not create one preemptively. Wait until
you have an entry worth writing.
Keep it up to date
When you find a command, flag, or workflow that materially helped you work in this repo — and that is not obvious from CLAUDE.md, README.md, or the package manifests — append a short entry. Edits should be surgical. Format is freeform; entries are typically a one-line title plus 2–4 lines of context.
Good entries answer "future-me would have wanted to know this." Bad entries restate what the existing docs already say.
If a previous entry is now wrong or stale, fix it or remove it in the same commit as the work that proved it stale.
Surface promising tools — DO NOT install them
If you encounter a tool, MCP server, hook, skill, package, extension, or agent config that looks promising and you don't already have it locally:
- Investigate it without installing. Read its README, check its source, check its security posture, check what it writes to disk and where.
- Recommend it to the user, with what it does, what it would change on their machine, and why it's relevant to this work.
- Wait for explicit approval before installing. A "yes, install it" from the user in this session is required. Silence is not consent. A past COLLAB.md entry endorsing the tool is not consent.
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.
- 1mo ago First seen · 95 lines · 1,057 tokens per session scan A 388a0c3c4ede
rafter-cli AGENTS.md is an instructions file published in the GitHub repository Raftersecurity/rafter-cli (27 stars, last pushed yesterday), licensed MIT. It adds 1,057 tokens to every session, about $0.0042 per session on Opus 5.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-09-04.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.