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.
git clone --depth 1 https://github.com/karlkfi/claude-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/plugins/karlkfi/claude-bouncer/exit-status-guard)<a href="https://agentmods.dev/plugins/karlkfi/claude-bouncer/exit-status-guard"><img src="https://agentmods.dev/badge/plugins/karlkfi/claude-bouncer/exit-status-guard/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/plugins/karlkfi/claude-bouncer/exit-status-guard"><img src="https://agentmods.dev/badge/plugins/karlkfi/claude-bouncer/exit-status-guard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
exit-status-guard 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 9d 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
{
"name": "exit-status-guard",
"version": "2.0.1",
"description": "Deny shell commands whose exit status is the answer and gets lost.",
"author": {
"name": "Karl",
"url": "https://github.com/karlkfi"
},
"homepage": "https://github.com/karlkfi/claude-bouncer/tree/main/plugins/exit-status-guard",
"repository": "https://github.com/karlkfi/claude-bouncer",
"license": "MIT",
"keywords": [
"claude-code",
"hooks",
"guardrail",
"bash",
"zsh",
"shell",
"pipeline",
"pipestatus",
"exit-status",
"ci",
"gate",
"false-green",
"background",
"verification",
"command"
]
}
What it installs
The manifest is a name and a version. 1 command travel with it, and installing the plugin installs all of them — 18 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 9d ago First seen · 30 lines scan A f8ae23003993
exit-status-guard is a plugin published in the GitHub repository karlkfi/claude-bouncer (3 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
code-refactoring
Code cleanup, refactoring automation, and technical debt management with context restoration.
codebase-cleanup
Technical debt reduction, dependency updates, and code refactoring automation.
debugging-toolkit
Interactive debugging, developer experience optimization, and smart debugging workflows.
distributed-debugging
Distributed system tracing and debugging across microservices.
senior-engineering-partner
A strict code reviewer, pair programmer, debugger, and mentor for Python, Bash, Google Apps Script, and JavaScript — a security-first, phase-aware engineering discipline with an enforced spec → plan → TDD → verify workflow.
pi-delegate
Delegate implementation and tests to a local pi agent (using your own pi provider/model), with enforced dispatch discipline.