aibadger AGENTS.md

Project-specific instructions for working on PVRLabs/aibadger, a Go codebase. They describe where code belongs, which checks to run, and how release files should be handled.

In plain words
What is it for?
Making scoped changes in the aibadger repository, formatting and testing Go code, running builds or checks, and avoiding mistakes in release packaging.
Why use it?
They give an agent the repository’s local rules so changes follow its structure and verification practices.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/pvrlabs/aibadger/agents-md
Clone the repo
git clone --depth 1 https://github.com/PVRLabs/aibadger

Made for: Codex, OpenCode.

Per session 368 This file is loaded in full into every session.
When invoked 368 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00368 $0.00368
Opus 5 $0.00184 $0.00184
Sonnet 5 $0.00074 $0.00074
Haiku 4.5 $0.00037 $0.00037

Measured 3d ago against content hash 3dc42a69b6cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

AGENTS.md · 43 lines

What it actually says

AIBadger Agent Guidance

Scope and context

Prefer existing repository patterns and keep changes scoped to the request.

Use repo-map to locate related repositories only when work crosses repository boundaries. For a Homebrew formula update, edit Formula/badger.rb in homebrew-tap. Use repo-map get homebrew-tap when that name is registered; otherwise clone the tap. See docs/releasing.md.

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>.

Changes

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.

  1. 3d ago First seen · 43 lines · 368 tokens per session scan A 3dc42a69b6cf

Subscribe to this mod's changes

aibadger AGENTS.md is an instructions file published in the GitHub repository PVRLabs/aibadger (27 stars, last pushed 3d ago), licensed MIT. It adds 368 tokens to every session, about $0.0018 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-08-30.