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 skills add brennhill/Kaboom-Browser-AI-Devtools-MCP --skill kaboom-connection-guardgit clone --depth 1 https://github.com/brennhill/Kaboom-Browser-AI-Devtools-MCPWrote 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/skills/brennhill/kaboom-browser-ai-devtools-mcp/kaboom-connection-guard)<a href="https://agentmods.dev/skills/brennhill/kaboom-browser-ai-devtools-mcp/kaboom-connection-guard"><img src="https://agentmods.dev/badge/skills/brennhill/kaboom-browser-ai-devtools-mcp/kaboom-connection-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/skills/brennhill/kaboom-browser-ai-devtools-mcp/kaboom-connection-guard"><img src="https://agentmods.dev/badge/skills/brennhill/kaboom-browser-ai-devtools-mcp/kaboom-connection-guard.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.00030 | $0.01007 |
| Opus 5 | $0.00015 | $0.00504 |
| Sonnet 5 | $0.00006 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
kaboom-connection-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 11d 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
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 11d ago First seen · 123 lines · 30 tokens per session scan A 84e29eeb5209
kaboom-connection-guard is a skill published in the GitHub repository brennhill/Kaboom-Browser-AI-Devtools-MCP (65 stars, last pushed 3d ago), licensed AGPL-3.0. It adds 30 tokens to every session and 1,007 once invoked, about $0.0002 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-30.
Other skills, from other repositories
health
Fast platform health check. Designed to fit in under 1 KB output, so it's cheap to run on every chat turn if desired.
auto-fix
Auto-diagnose + try-to-fix common problems.
debug-workflow
Systematically debug failing n8n workflows — expression errors, node type mismatches, pinned data issues, sub-workflow failures, authentication problems, rate limit errors, and silent data loss. Use this skill whenever the user reports an n8n workflow problem — phrases like "my n8n workflow is failing", "this…
preflight
Plan-vs-codebase validation — verifies API contracts, type names, field accuracy, dependencies, and paths before implementation begins.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
error-handling
Error handling patterns for Python and TypeScript applications. Use when designing error hierarchies, implementing retry logic, building error boundaries, or establishing logging strategies. Covers custom exceptions, result types, circuit breakers, and user-facing error messages.