Kevin Veen-BirkenbachandClaude Opus 5.5
de8823e239
kvb-org-operator collects the steps that wait on a human across all agents: commands under a deny or unconfirmed ask rule, anything outside the sandbox (keys, permission settings, foreign hosts, root), steps the agent rules reserve for the operator (push, release, tags, reboot) and human-bound ones (hardware key, login, second factor, purchase, decision). Sources are the own session, the kvb-org-rasci register and one message per live peer. Done steps drop out, duplicates merge, the rest is ordered by dependency and printed as a table plus one copyable bash block, then recorded as operator/<slug> register tasks. Agents never run a listed command or hand it to a peer. Operator order 2026-11-03; four descriptions trimmed for the listing budget. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
name, description
| name | description |
|---|---|
| kvb-check-security | Run the MEDUSA scanner (medusa-security) on a repository, working tree or secret stores. Use for security scans, vetting a repo, leaked secrets in chat or shell history, or /kvb-check-security. Defensive only. |
MEDUSA is a defensive AI-first security scanner (40,000+ patterns: CVEs, prompt injection, MCP tool poisoning, leaked secrets).
Setup
Check availability with medusa --version.
If missing, install it with pipx install medusa-security (fallback: pip install --user medusa-security).
Commands
| Task | Command |
|---|---|
| Scan the current project | medusa scan . |
Vet a remote repo BEFORE cloning (supply chain, poisoned .claude/ hooks, permissions, skills) |
medusa scan --git <url-or-org/repo> |
| Find leaked API keys in AI chat + shell history | medusa secrets scan |
| Scan one exported file | medusa secrets scan --path <file> |
Rules
- Run scans read-only; never pass
--revealand never runmedusa secrets purgeunless the user explicitly asks for it. - Summarize findings by severity with file/line references; do not paste secret values into the conversation, even redacted ones.
- Treat findings as signals for review, not verdicts; confirm true positives in the code before proposing fixes.
- Vet third-party agent repos (
medusa scan --git) before recommending the user clone or install them.