Borrowing it
Nothing to install: this file belongs to PVRLabs/aibadger. 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/PVRLabs/aibadger/main/AGENTS.mdgit clone --depth 1 https://github.com/PVRLabs/aibadgerWrote 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/pvrlabs/aibadger/agents-md)<a href="https://agentmods.dev/instructions/pvrlabs/aibadger/agents-md"><img src="https://agentmods.dev/badge/instructions/pvrlabs/aibadger/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/pvrlabs/aibadger/agents-md"><img src="https://agentmods.dev/badge/instructions/pvrlabs/aibadger/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.00344 | $0.00344 |
| Opus 5.5 | $0.00138 | $0.00138 |
| Sonnet 5.5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
aibadger 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 29d 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
AIBadger Agent Guidance
Scope and context
Prefer existing repository patterns and keep changes scoped to the request.
Use RepoLink (repolink) to locate related repositories only when work
crosses repository boundaries.
Go and verification
Use the Go version declared in go.mod. The public facade is pkg/badger;
implementation code is under internal/ and cmd/badger.
During iteration, prefer focused package or test runs. Before finishing a
change, format touched Go files and run verification appropriate to its scope.
For Go test execution, follow the lite-tools skill. Run go vet ./... when
the change affects the repository broadly. Do not add project-local formatter
or linter tooling unless asked.
Useful commands:
go build ./...
gofmt -w <changed-go-files>
go vet ./...
Artifacts and releases
Do not commit ignored local binaries (/badger, /badger-release, *.test,
/bin/badger), hand-edit release archives/checksums/installer trees, or change
release packaging metadata unless the task is a release or tap update.
Default builds are development builds. Release builds use the
aibadger_release tag and profiling builds use aibadger_profile; see
docs/releasing.md for release-specific details.
When a commit is tied to a named plan, include Plan: <plan name>.
Archived private plans
Move full private historical plans to Projctl under
archive/<project-id>/plans/. Keep a short description and pointer in the
source archive folder.
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.
- 29d ago Changed · +6 lines · +41 tokens per session 66683460b16f
- 1mo ago Changed · -3 lines · -65 tokens per session 1f7364a4bf77
- 1mo ago First seen · 43 lines · 368 tokens per session scan A 3dc42a69b6cf
aibadger AGENTS.md is an instructions file published in the GitHub repository PVRLabs/aibadger (77 stars, last pushed today), licensed MIT. It adds 344 tokens to every session, about $0.0014 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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.