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.
npx agentmods add instructions/vncent786/bounty-api/agents-mdgit clone --depth 1 https://github.com/vncent786/bounty-apiWhat 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 | $0.04506 | $0.04506 |
| Opus 5 | $0.02253 | $0.02253 |
| Sonnet 5 | $0.00901 | $0.00901 |
| Haiku 4.5 | $0.00451 | $0.00451 |
Grade A, and why
bounty-api 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 212 lines · 4,506 tokens per session scan A 718b71172de2
bounty-api AGENTS.md is an instructions file published in the GitHub repository vncent786/bounty-api (1 stars, last pushed 2d ago), with no licence file. It adds 4,506 tokens to every session, about $0.0225 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
x402-backend CLAUDE.md
Instructions for Wintyx57/x402-backend, covering x402 bazaar - contexte pour claude, vue d'ensemble, cli x402-bazaar (milestone 1 - complet, publie sur npm), architecture and deploiements.
geolens CLAUDE.md
Instructions for geolens-io/geolens: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
deckforge CLAUDE.md
Instructions for Whatsonyourmind/deckforge, covering deckforge, tech stack, project structure, key commands and local development.
dev-challenge CLAUDE.md
Instructions for micheltlutz/dev-challenge, covering claude.md, the one rule to internalise, slash commands, subagents and skills.
Axon developer.instructions.md
Instructions for jyunming/Axon, covering role: developer, core conventions, document schema — never deviate, config.yaml → dataclass mapping and adding a new loader.
Axon security-auditor.instructions.md
Instructions for jyunming/Axon, covering role: security auditor, known risk areas in this codebase, 1. bm25 serialization — src/axon/retrievers.py, 2. path traversal — src/axon/api.py /ingest endpoint and 3. dependency cves.