Borrowing it
Nothing to install: this file belongs to Mimirs402/bountyverdict. 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/Mimirs402/bountyverdict/main/AGENTS.mdgit clone --depth 1 https://github.com/Mimirs402/bountyverdictWrote 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/mimirs402/bountyverdict/agents-md)<a href="https://agentmods.dev/instructions/mimirs402/bountyverdict/agents-md"><img src="https://agentmods.dev/badge/instructions/mimirs402/bountyverdict/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.00324 | $0.00324 |
| Opus 5 | $0.00162 | $0.00162 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
bountyverdict 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- bountyverdict AGENTS.md — 100% identical, 0 lines differ
What it actually says
Repository agent instructions
- Treat customer revenue and genuine purchases as onchain, non-owner settlement facts only. Never infer either from HTTP traffic, directory probes, search ranks, installs, owner canaries, or marketplace auditions.
- Every direct request made by maintainers or automated audits to the production Worker must send
User-Agent: bountyverdict-owner-audit/1.0unless a more specific existingbountyverdict-*owner user agent already applies. - Directory and marketplace searches can trigger server-side origin crawls whose user agent cannot be controlled. Run broad live retrieval audits only through
run-audited-monitor.ts, which must establish or reuse an explicit trusted-funnel draining rotation; do not describe traffic collected during that window as organic demand. - Never self-install, self-pay, or fabricate traffic to improve acquisition metrics. Read-only retrieval benchmarks must be labeled owner-run.
- Do not issue a payment challenge for structurally invalid input. Canonical POST routes must validate a complete JSON body before returning HTTP 402; discovery belongs in OpenAPI and
/.well-known/x402. - Standard x402 authorization binds a resource URL, not a POST body. Preserve the validated JSON on retry, expose an advisory normalized-body hash, and never claim cryptographic body binding.
- Use
npx [email protected]for Agentic Wallet commands. Inspect the challenge and enforce the exact atomic cap before any authorized owner canary. - Keep secrets outside Git.
.dev.varsand user configuration files are local-only and must remain ignored with mode0600where supported.
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.
- 6d ago First seen · 11 lines · 324 tokens per session scan A 91afb3ad74a2
bountyverdict AGENTS.md is an instructions file published in the GitHub repository Mimirs402/bountyverdict (1 stars, last pushed 1mo ago), licensed MIT. It adds 324 tokens to every session, about $0.0016 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-31.
Other instructions, from other repositories
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.
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).
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).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.