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/shrwnsan/vibekit-claude-pluginsWrote 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/agents/shrwnsan/vibekit-claude-plugins/the-incident-responder)<a href="https://agentmods.dev/agents/shrwnsan/vibekit-claude-plugins/the-incident-responder"><img src="https://agentmods.dev/badge/agents/shrwnsan/vibekit-claude-plugins/the-incident-responder/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/agents/shrwnsan/vibekit-claude-plugins/the-incident-responder"><img src="https://agentmods.dev/badge/agents/shrwnsan/vibekit-claude-plugins/the-incident-responder.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.00117 | $0.01059 |
| Opus 5 | $0.00059 | $0.00530 |
| Sonnet 5 | $0.00023 | $0.00212 |
| Haiku 4.5 | $0.00012 | $0.00106 |
Grade A, and why
the-incident-responder 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 yesterday.
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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- yesterday First seen · 63 lines · 117 tokens per session scan A 2b3f429c604d
the-incident-responder is an agent published in the GitHub repository shrwnsan/vibekit-claude-plugins (7 stars, last pushed yesterday), with no licence file. It adds 117 tokens to every session and 1,059 once invoked, about $0.0006 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-09-10.
Other agents, from other repositories
debugger
Use this agent to diagnose and fix bugs from error messages, stack traces, or unexpected behavior. Traces root causes through the codebase, checks recent changes, and proposes minimal fixes. Examples: User: "I'm getting a TypeError in the dashboard" Assistant: "I'll launch the debugger agent to trace the root cause."…
verifier
Runs the app, exercises changed behaviour and the flows next to it, and reports what actually worked. Use after implementing a change and before showing it to a human. Reports only - it never fixes anything.
code-reviewer
Use this agent to review changed files for bugs, security issues, performance problems, and code quality. Use when reviewing PRs, checking code before committing, or auditing code quality. Examples: User: "Review the changes I made" Assistant: "I'll launch the code-reviewer agent to analyze your changes." User: "Is…
context-advisor
Use this agent to assess context window health and recommend compaction or session management strategies. Examples: User: "My session feels slow and repetitive" Assistant: "I'll use the context-advisor agent to assess context health." User: "Should I compact or start fresh?" Assistant: "Let me launch the…
manifest-curator
Review the actual Claude or Codex manifests, catalogs and pinned revisions against their own schemas. Audit by default; report evidence and uncertainty.
doc-consistency-reviewer
Audit plugin README parity, platform-specific benchmark evidence and community documentation against Foundry's shared rules. Read-only; report GOOD/FLAG findings.