Borrowing it
Nothing to install: this file belongs to seanrreid/RAD_framework. 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/seanrreid/RAD_framework/main/AGENTS.mdgit clone --depth 1 https://github.com/seanrreid/RAD_frameworkWrote 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/seanrreid/rad_framework/agents-md)<a href="https://agentmods.dev/instructions/seanrreid/rad_framework/agents-md"><img src="https://agentmods.dev/badge/instructions/seanrreid/rad_framework/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/seanrreid/rad_framework/agents-md"><img src="https://agentmods.dev/badge/instructions/seanrreid/rad_framework/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.01117 | $0.01117 |
| Opus 5.5 | $0.00447 | $0.00447 |
| Sonnet 5.5 | $0.00223 | $0.00223 |
| Haiku 4.5 | $0.00112 | $0.00112 |
Grade A, and why
RAD_framework 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 17d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context
Project conventions for every coding agent. Codex reads this file natively; Claude Code loads it through the
@AGENTS.mdimport inCLAUDE.md. Fill in every section. Accurate AGENTS.md = fewer corrections. Seedocs/architect-guide.mdfor maintenance guidance.
Project
Name: Description: Status:
Stack
| Layer | Technology |
|---|---|
| Backend | |
| Frontend | |
| Database | |
| Testing | |
| Package manager |
Project Structure
[describe your directory layout here]
Commands
# Install
# Run (development)
# Run tests
# Run E2E tests
Architecture Decisions
Coding Conventions
- Every behavior change ships a test in the same commit — new scripts get a co-located
test-<name>.shfixture; harness changes extendharness/test/*.test.js; a task with no testable surface says so explicitly in its Validate field - Functions stay under ~40 lines with intent-revealing names; magic values become named constants at the top of the file; comments state constraints, not narration
- Never swallow errors: every catch/
|| trueeither rethrows, exits non-zero, or logs the reason with context; fail-closed is the default at every gate or check boundary - Edge cases are named in the task's Validate field before implementation (empty input, missing field, zero/negative, non-array) and each gets an explicit test case
Testing Standards
What the Agent Must Never Do
- Never commit secrets, tokens, or credentials
- Never assume a library exists — only use packages in the package file
- Never execute /rad-deliver without an
approvedevent in.agents/state/<feature>/events.jsonl(the gate authority, appended by /rad-approve). The plan doc'sStatus: approvedheader is a display-only mirror, not the gate. Approval is checked byrad deliverand the gate, not by prose alone. - Never read
.agents/plans/,.agents/research/or.agents/logs/unless the task names them — completed specs describe past intent and can be mistaken for current requirements
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.
- 17d ago Changed · +1 lines · +41 tokens per session 4241da3626aa
- 20d ago Changed · +4 lines · +91 tokens per session bf1158741a00
- 21d ago Changed · +10 tokens per session ca3035ba967a
- 23d ago First seen · 136 lines · 975 tokens per session scan A 4f4ec87fb00c
RAD_framework AGENTS.md is an instructions file published in the GitHub repository seanrreid/RAD_framework (5 stars, last pushed 4d ago), licensed MIT. It adds 1,117 tokens to every session, about $0.0045 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-10-06.
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.