Borrowing it
Nothing to install: this file belongs to emersonjds/redbar. 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/emersonjds/redbar/main/AGENTS.mdgit clone --depth 1 https://github.com/emersonjds/redbarWrote 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/emersonjds/redbar/agents-md)<a href="https://agentmods.dev/instructions/emersonjds/redbar/agents-md"><img src="https://agentmods.dev/badge/instructions/emersonjds/redbar/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.01456 | $0.01456 |
| Opus 5 | $0.00728 | $0.00728 |
| Sonnet 5 | $0.00291 | $0.00291 |
| Haiku 4.5 | $0.00146 | $0.00146 |
Grade A, and why
redbar 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 2d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent instructions — redbar
Read by Claude Code, Codex, Cursor, Windsurf and Copilot.
CLAUDE.mdand.github/copilot-instructions.mdpoint here so there is one source of truth, not five.
What this project is
redbar finds the test-coverage gaps in what a branch changed, and hands them to an agent to fill.
The analysis calls no model. It reads the coverage report the project already produces, crosses
it with git diff, and ranks what nothing executes. That is not purism — it is where the number's
authority comes from. A wrong number from a model is bad; a wrong number from a regex is worse,
because it arrives wearing the compiler's uniform.
The rules that govern every change here
- Zero LLM in
src/. No AI SDK, no model API call, no agent spawn in the analysis path. CI does not enforce this — you do. - Zero runtime dependencies.
dependenciesinpackage.jsonstays empty. CI fails the build if one appears. The coverage parsers are hand-written on purpose; do not reach for an XML library. - Adding a language is ONE LINE of data in
src/languages.ts. If you are about to writeswitch (lang)orif (lang.id === 'rust')anywhere outside that table, stop — the design has failed and the fix is to move the difference into the registry as data. - Purity.
src/coverage/*,src/symbols.ts,src/classify.ts,src/gap.tsnever touch disk and never spawn a process. Onlydetect.ts,git.ts,runner.ts,engine.ts,cli.tsmay. - Deterministic output. Same input, same order, byte for byte. A report that reshuffles cannot be diffed in a PR, and the CI gate would flap.
- Never install anything into a user's project.
initprints the command; the human runs it. - The agent never grades itself.
executeis the only command that calls a model. Every verdict it produces exceptneeds-human,timeout, andno-outputis measured — by git, by a regex, by the test runner, or by a fresh coverage report. If you are about to let the agent's own output decide whether a gap closed, stop: that is the failure this whole project exists to prevent, reintroduced one layer down.
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.
- 2d ago First seen · 105 lines · 1,456 tokens per session scan A 13451c54a2f6
redbar AGENTS.md is an instructions file published in the GitHub repository emersonjds/redbar (6 stars, last pushed 2d ago), licensed MIT. It adds 1,456 tokens to every session, about $0.0073 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-09-04.
Other instructions, from other repositories
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core, parameterized queries, migration strategy.
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).