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 agentmods add skills/vmihalis/hacker-bob/bob-debugnpx skills add vmihalis/hacker-bob --skill bob-debuggit clone --depth 1 https://github.com/vmihalis/hacker-bobWhat 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 | $0.00021 | $0.01842 |
| Opus 5 | $0.00010 | $0.00921 |
| Sonnet 5 | $0.00004 | $0.00368 |
| Haiku 4.5 | $0.00002 | $0.00184 |
Grade A, and why
bob-debug 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the read-only post-session debugger for Bob. Review a completed or stuck Hacker Bob session and explain pipeline quality, drift, failures, and concrete improvements. Do not evaluate, verify, grade, report, mutate state, or interact with the target.
Input: $ARGUMENTS (--last, no args, <target_domain>, optionally plus --deep, or --diff-attempts <prev> <curr> for cross-attempt v2 inspection)
Hard Rules
- Read-only only. Never call mutating MCP tools, never write files, never merge waves, never transition phases, never update auth, never write reports, and never use HTTP scan or browser/target interaction tools.
- Do not use the
Tasktool by default. Debug locally from telemetry, MCP reads, artifacts, and narrow transcript windows. - Do not create a debug bundle in v1. Print the assessment only.
- Telemetry MCPs are the first source of truth. Artifacts and transcripts are supporting evidence.
Argument Handling
- No args or
--last: inspect the latest local session under~/hacker-bob-sessions. <target_domain>: inspect that specific session directory.--deep: additionally inspect Claude transcript windows around flagged issues.--diff-attempts <prev> <curr>: cross-attempt v2 verification diff. Each token is either an archive id frombob_read_verification_context.data.archived_attempts[*].attempt_id, or the literal stringcurrentfor the live attempt. Callsbob_diff_verification_attempts({ target_domain, attempt_a: <prev>, attempt_b: <curr> })and prints the snapshot / adjudication / final hash matches plus the per-file divergence (only-in-a, only-in-b, and content-changed entries with truncated 16-char hashes). Use this to explain why a re-verification produced different results across attempts.- If both a domain and
--deepare present, debug that domain deeply. If multiple non-flag tokens are present, stop and ask for one target domain.
Latest-session detection must pick the newest target directory by pipeline-events.jsonl mtime. If no pipeline event file exists, fall back in order to state.json, grade.json, report.md, then directory mtime.
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.
- 3d ago First seen · 112 lines · 21 tokens per session scan A 945f2ea98ff5
bob-debug is a skill published in the GitHub repository vmihalis/hacker-bob (97 stars, last pushed 4d ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,842 once invoked, about $0.0001 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
mcpnuke-add-check
Create a new mcpnuke security check module end-to-end: pattern file, check function, wire into runallchecks, add tests, update changelog. Use when adding a new security check to mcpnuke.
mcpnuke-add-patterns
Add new regex detection patterns to mcpnuke's pattern libraries with test coverage. Use when adding new patterns to rules.py or probes.py, or when extending detection for a vulnerability class.
mcpnuke-add-transport
Add a new transport type to mcpnuke alongside SSE, HTTP, and ToolServer. Use when adding support for a new MCP transport protocol like DPoP, mTLS, or a custom gateway.
mcpnuke-extend-dvmcp
Add new DVMCP challenge test classes to mcpnuke's test suite following the established pattern. Use when adding tests for a new vulnerability type or DVMCP challenge.
mcpnuke-run-tests
Run mcpnuke's test suite, interpret failures, and fix issues. Use when running tests, debugging test failures, or verifying changes in mcpnuke.
fix-plan
Generate an EPSS/KEV-prioritised remediation plan from a scan. Returns the top findings ranked by real-world exploitation risk with copy-paste upgrade commands, semver-jump risk classification (PATCH/MINOR/MAJOR), and a recommendation per package. Use when the user asks for "what should I fix first", "remediation…