Borrowing it
Nothing to install: this file belongs to tylerjrbuell/reactive-agents. 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/tylerjrbuell/reactive-agents/main/AGENTS.mdgit clone --depth 1 https://github.com/tylerjrbuell/reactive-agentsWrote 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/tylerjrbuell/reactive-agents/agents-md)<a href="https://agentmods.dev/instructions/tylerjrbuell/reactive-agents/agents-md"><img src="https://agentmods.dev/badge/instructions/tylerjrbuell/reactive-agents/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.06277 | $0.06277 |
| Opus 5 | $0.03138 | $0.03138 |
| Sonnet 5 | $0.01255 | $0.01255 |
| Haiku 4.5 | $0.00628 | $0.00628 |
Grade A, and why
reactive-agents 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 — 789 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to AI Agents when working with code in this repository.
Quick Start Checklist
Before running ANY command in this repository:
- ✅ Use
poetry run <command>OR enterpoetry shellfirst - ❌ NEVER manually activate:
source .venv/bin/activate - ❌ NEVER run Python/pytest directly without
poetry run - ✅ Virtual environment is at
.venv/(managed by Poetry) - ✅ Check you're in project root:
/home/tylerbuell/Documents/AIProjects/reactive-agents
Example correct commands:
poetry run pytest # ✅ Correct
poetry run python playground/runner.py # ✅ Correct
poetry shell # ✅ Enters poetry environment
pytest # ✅ Now correct (inside shell)
python playground/runner.py # ✅ Now correct (inside shell)
Example WRONG commands:
pytest # ❌ Not in poetry environment
python playground/runner.py # ❌ Will fail with import errors
source .venv/bin/activate # ❌ Don't manually activate
Development Commands
Virtual Environment Setup
IMPORTANT: This project uses Poetry for dependency management.
The virtual environment is located at .venv/ in the project root.
# DO NOT manually activate the virtual environment
# Poetry handles this automatically with 'poetry run'
# WRONG - Don't do this:
source .venv/bin/activate
python script.py
# CORRECT - Use poetry run:
poetry run python script.py
poetry run pytest
# To run multiple commands in the poetry environment:
poetry shell # Opens a new shell with venv activated
# Now you can run commands directly:
pytest
python playground/runner.py
Key Points:
- Virtual environment:
.venv/(already created, don't recreate) - Python version: 3.10+ (check with
poetry run python --version) - Always prefix commands with
poetry runOR enterpoetry shellfirst - If you see import errors, you're likely not in the poetry environment
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 · 789 lines · 6,277 tokens per session scan A 03b96b9cde33
reactive-agents AGENTS.md is an instructions file published in the GitHub repository tylerjrbuell/reactive-agents (5 stars, last pushed 7mo ago), licensed MIT. It adds 6,277 tokens to every session, about $0.0314 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.