Borrowing it
Nothing to install: this file belongs to TyrusRC/praetor. 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/TyrusRC/praetor/main/AGENTS.mdgit clone --depth 1 https://github.com/TyrusRC/praetorWrote 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/tyrusrc/praetor/agents-md)<a href="https://agentmods.dev/instructions/tyrusrc/praetor/agents-md"><img src="https://agentmods.dev/badge/instructions/tyrusrc/praetor/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/tyrusrc/praetor/agents-md"><img src="https://agentmods.dev/badge/instructions/tyrusrc/praetor/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.05434 | $0.05434 |
| Opus 5.5 | $0.02174 | $0.02174 |
| Sonnet 5.5 | $0.01087 | $0.01087 |
| Haiku 4.5 | $0.00543 | $0.00543 |
Grade A, and why
praetor 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 5d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Team Configuration
This project uses specialized agents for parallel pentesting. The orchestrator (main conversation) dispatches agents for independent work streams, merges results, and makes strategic decisions.
Definition Files
Each role below corresponds to a file in .claude/agents/<role>.md that the Agent tool auto-loads when dispatched by name. Update both this file (role overview) AND the agent file (operational detail) when changing a role.
Host-agnostic access. The Agent-tool dispatch above is Claude-Code-native, but the playbooks themselves are portable: any MCP host reaches them as tools via list_agents() / get_agent("<role>"). A host that spawns its own sub-agents (e.g. DeepSeek Harness) gives each one a get_agent playbook as its system prompt — the same roles, same tools, driven by that host's model. list_agents() returns a host-agnostic tier per role (strategic / standard / fast, from the Claude model pin) — a non-Claude host maps that tier to its nearest model instead of the opus/sonnet/haiku name it can't resolve; a single-model host runs everything on that model and Rule 33's Opus escalation becomes a no-op. Parallel dispatch is the one host-provided piece; single-threaded hosts run the roles sequentially with the orchestration tools (get_hunt_plan / get_next_action / route_signals / judge_completion).
The orchestrator role is split out: grow-agent is the session-lifecycle orchestrator, defined in .claude/agents/grow-agent.md. When invoked, grow-agent dispatches the worker roles below (including the network and cloud lane owners).
Command Tier (above grow-agent)
Two engagement leads sit above grow-agent. They own strategy — research, a written plan, multi-domain dispatch, cross-target synthesis, delivery — and do NOT run the per-domain loop themselves. Both invoke the shared SOP .claude/skills/command-engagement.md; each agent file carries only its role deltas. On-demand only.
{pentest|redteam}-commander engagement lead — research, plan, synthesize, report
└─ grow-agent(domain) × N per-domain executor (bounded: 2–3 in flight)
└─ workers (web + network + cloud + mobile lanes)
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.
- 5d ago Changed · +14 lines · +536 tokens per session bc0bce75f109
- 17d ago Changed · -3 tokens per session e0aced70d3b4
- 19d ago Changed · +7 lines · +201 tokens per session 96460577586c
- 27d ago Changed · +14 tokens per session 751e1a0049c1
- 1mo ago Changed · +16 lines · +598 tokens per session ab265c7d301d
- 1mo ago Changed · +1 lines · +144 tokens per session 6989db740251
- 1mo ago Changed · +7 lines · +449 tokens per session aa452b129a7a
- 1mo ago First seen · 207 lines · 3,495 tokens per session scan A d9ee657fd90f
praetor AGENTS.md is an instructions file published in the GitHub repository TyrusRC/praetor (7 stars, last pushed today), licensed Apache-2.0. It adds 5,434 tokens to every session, about $0.0217 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-08-31.
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.