Borrowing it
Nothing to install: this file belongs to nugehs/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/nugehs/bouncer/main/AGENTS.mdgit clone --depth 1 https://github.com/nugehs/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/nugehs/bouncer/agents-md)<a href="https://agentmods.dev/instructions/nugehs/bouncer/agents-md"><img src="https://agentmods.dev/badge/instructions/nugehs/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/nugehs/bouncer/agents-md"><img src="https://agentmods.dev/badge/instructions/nugehs/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.00346 | $0.00346 |
| Opus 5.5 | $0.00138 | $0.00138 |
| Sonnet 5.5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00035 | $0.00035 |
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 13d 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 agent guide
Mission and boundary
bouncer is a deterministic static checker for code-level controls required by regulatory rule packs. It produces file-and-line evidence and must distinguish a verified control, a missing control, and an unknown/unlocatable surface honestly. A green result is not legal certification.
The marketing site is a separate repository at /Users/segzy/dev/bouncer-web. Do not edit it unless the task explicitly includes that repository.
Working safely
- Preserve the current branch and all existing work. Check
git status --short --branchfirst. - Use npm and keep
package-lock.jsonauthoritative. - Do not publish, bump versions, or change package/server metadata unless explicitly asked.
- Treat rule identifiers, JSON fields, CLI exit codes, evidence locations, config, and MCP tools as public interfaces.
- Do not weaken a control merely to make a sample repository pass; fix detection or document the limitation.
Code map
src/cli.js: CLI entry and command orchestration.src/: repository scanning, rule evaluation, evidence, reporting, and MCP support.tests/: Node test-runner suites and fixtures.scripts/: version/release metadata helpers.
Keep the engine regulation-agnostic and rule-pack behaviour explicit. Regulatory wording and mappings require source-backed review. Preserve unknown when the static evidence is insufficient; do not infer compliance from filenames or weak keywords alone.
Validation
Run:
npm test
For CLI changes, verify check, doctor, terminal/JSON output, and non-zero gate behaviour. For MCP changes, keep stdout protocol-clean and diagnostics on stderr.
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.
- 13d ago First seen · 35 lines · 346 tokens per session scan A 26a0fb11346e
bouncer AGENTS.md is an instructions file published in the GitHub repository nugehs/bouncer (1 stars, last pushed 2d ago), licensed MIT. It adds 346 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-10-14.
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.