Borrowing it
Nothing to install: this file belongs to karanb192/bouncer. 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/karanb192/bouncer/main/AGENTS.mdgit clone --depth 1 https://github.com/karanb192/bouncerWrote 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/karanb192/bouncer/agents-md)<a href="https://agentmods.dev/instructions/karanb192/bouncer/agents-md"><img src="https://agentmods.dev/badge/instructions/karanb192/bouncer/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/karanb192/bouncer/agents-md"><img src="https://agentmods.dev/badge/instructions/karanb192/bouncer/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.00461 | $0.00461 |
| Opus 5.5 | $0.00184 | $0.00184 |
| Sonnet 5.5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
bouncer 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 1mo 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
Bouncer is active
A door-guard sits in front of your shell. Every run_shell_command call passes
the door before it runs; destructive commands are blocked by an enforced
BeforeTool hook, not by you, and not negotiable.
Don't try to run the footguns below. They will be bounced with the exact rule that fired, and the turn is wasted. Reach for the safe alternative instead.
Bounced at the door (non-exhaustive):
rm -rf ~,rm -rf /,rmon system dirs or with parent-traversal / glob targetsdd/mkfs/wipefsto a disk device; writing to/dev/sd*,/dev/nvme*- overwriting
/etc/passwd,/etc/shadow,/etc/sudoers,/etc/hosts DROP TABLE/DROP DATABASE/TRUNCATE;DELETE/UPDATEwith noWHEREredis-cli flushall/flushdb,dropdbcurl … | sh(piping a URL straight to the shell);curl/wgetto paste / exfil hosts- uploading or
cat-ing secrets:.env,id_rsa,*.pem,*.key, credentials git push --forceto main/master,git reset --hard,git clean -f,git checkout .chmod 777,chown /,kill -9 1, fork bombs,npm publish,crontab -r
Walk right in: read-only inspection, scoped edits, git status/diff/add/commit,
tests, builds, a WHERE'd UPDATE, normal npm/docker/psql work.
This advisory is belt-and-suspenders. The real enforcement is the hook, but
not provoking it keeps your turns productive. Tune with
BOUNCER_LEVEL=critical|high|strict; disable with BOUNCER_OFF=1.
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.
- 1mo ago First seen · 28 lines · 461 tokens per session scan F 146eb0f7ef83
bouncer AGENTS.md is an instructions file published in the GitHub repository karanb192/bouncer (5 stars, last pushed 2mo ago), licensed MIT. It adds 461 tokens to every session, about $0.0018 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-31.
Other instructions, from other repositories
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core 10, parameterized queries, migration strategy.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
plan-forge caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
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).