Borrowing it
Nothing to install: this file belongs to loncadev/baron. 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/loncadev/baron/main/AGENTS.mdgit clone --depth 1 https://github.com/loncadev/baronWrote 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/loncadev/baron/agents-md)<a href="https://agentmods.dev/instructions/loncadev/baron/agents-md"><img src="https://agentmods.dev/badge/instructions/loncadev/baron/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/loncadev/baron/agents-md"><img src="https://agentmods.dev/badge/instructions/loncadev/baron/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.00529 | $0.00529 |
| Opus 5.5 | $0.00212 | $0.00212 |
| Sonnet 5.5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
baron 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 2mo 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.
What it actually says
Work tracking — route through Baron
Track work through Baron, not raw provider writes: it normalizes issues and source control across providers behind one contract, so speak its abstract vocabulary, never a vendor's native states.
- Roles, not native states. Move work by role:
backlog → ready → in_progress → in_review → done, plusblocked. Say "move it to in_progress", never "set the state to Active" — Baron maps the role to the provider. - Type roles this policy maps:
initiative,epic,story,task,bug,subtask. Asking for one it does not map is an error, not a degrade — that list is whatissue.createaccepts here. - Tools:
baron_issue_*(create / get / update / transition / comment / assign / link / query),baron_scm_*(branch / PR),baron_recipe_run, andbaron_learning_*/baron_followup_*for durable decisions and follow-ups. - Daily loop — prefer the skills:
/baron:task-new(create),/baron:task-start <id>(cut the canonical branch, move to in_progress, assign you),/baron:task-finish(draft PR),/baron:task-land(undraft + merge — nevergh/az),/baron:task-move,/baron:task-list,/baron:task-sync. Each item's canonical branch is Baron-derived — use it verbatim, never invent one. - Reading/exploring a provider natively is fine, but make every work-item change through Baron so the role mapping, gap policy, and knowledge loop apply.
On this project (provider: github): roles ride labels (Baron provisions in-progress / in-review / done); sprints are NOT available — sprint queries degrade to empty. That empty is expected here, not a bug;
parent/child is emulated via a parent:<id> label. Where a capability is missing Baron negotiates it (error / emulate /
degrade) and logs it — an empty or emulated result from a degraded capability is expected behavior,
not a silent failure to report as a bug.
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.
- 2mo ago First seen · 29 lines · 529 tokens per session scan A bdeab5d7fd7e
baron AGENTS.md is an instructions file published in the GitHub repository loncadev/baron (1 stars, last pushed 23d ago), licensed Apache-2.0. It adds 529 tokens to every session, about $0.0021 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.