Borrowing it
Nothing to install: this file belongs to r5rana/agentware. 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/r5rana/agentware/main/AGENTS.mdgit clone --depth 1 https://github.com/r5rana/agentwareWrote 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/r5rana/agentware/agents-md)<a href="https://agentmods.dev/instructions/r5rana/agentware/agents-md"><img src="https://agentmods.dev/badge/instructions/r5rana/agentware/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/r5rana/agentware/agents-md"><img src="https://agentmods.dev/badge/instructions/r5rana/agentware/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.03997 | $0.03997 |
| Opus 5.5 | $0.01599 | $0.01599 |
| Sonnet 5.5 | $0.00799 | $0.00799 |
| Haiku 4.5 | $0.00400 | $0.00400 |
Grade A, and why
agentware 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Canonical Methodology (Deterministic Steering Format)
Single source of truth for agent behaviour. Loaded as always-on context because the auto-loaded
CLAUDE.mdimports it with@AGENTS.md. The agentware subagents reference it too. Rationale and examples live indocs/methodology.md(NOT agent-loaded). Every rule is atomic, carries a stable ID, and is enforced byscripts/agentware steering lint.agentware ships ZERO personal data. The knowledge base lives in an EXTERNAL directory the operator chose at onboarding. Resolve it with
scripts/agentware config --knowledge-dir-only; NEVER hardcode its path.
Execution loop
Every task runs this loop. Do not skip steps; do not stop until all subtasks are done.
- PLAN — break the task into verifiable subtasks; save the plan.
- EXECUTE — run commands / write code for one subtask.
- VERIFY — confirm it works with the project's own build/test/health command.
- NEXT — move to the next subtask.
- REPEAT — until every subtask is complete.
- COMPLETE — update the knowledge base, then present results.
Build and complete
- MUST treat building and completing tasks as the primary job. [R-EXEC-01]
- NEVER mark a task complete while any subtask is in progress or unverified. [R-EXEC-02]
- ALWAYS ask "is the original goal fully achieved?" before presenting results. [R-EXEC-03]
- IF something is bootstrapping THEN wait and verify; NEVER defer it to the user. [R-EXEC-04]
- IF a step failed THEN fix it and retry; NEVER present failure as completion. [R-EXEC-05]
- IF blocked by a dependency not resolvable under R-AUTO-01 THEN document the blocker and ask the user. [R-EXEC-06]
- ALWAYS track ongoing work in the worklog and plan status markers. [R-EXEC-07]
- NEVER pivot to a different approach mid-task without user approval; in-scope judgment is licensed by R-AUTO-01. [R-EXEC-08]
- ALWAYS update the knowledge base with what was built, what works, and gotchas after completion. [R-EXEC-09]
Planning
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 · 176 lines · 3,997 tokens per session scan A 1f7bd4dd7205
agentware AGENTS.md is an instructions file published in the GitHub repository r5rana/agentware (24 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 3,997 tokens to every session, about $0.0160 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-30.
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.