Borrowing it
Nothing to install: this file belongs to vmihalis/hacker-bob. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vmihalis/hacker-bob/main/.claude/skills/bob-debug/SKILL.mdgit clone --depth 1 https://github.com/vmihalis/hacker-bobWrote 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/vmihalis/hacker-bob/bob-debug)<a href="https://agentmods.dev/skills/vmihalis/hacker-bob/bob-debug"><img src="https://agentmods.dev/badge/skills/vmihalis/hacker-bob/bob-debug/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/vmihalis/hacker-bob/bob-debug"><img src="https://agentmods.dev/badge/skills/vmihalis/hacker-bob/bob-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.01842 |
| Opus 5.5 | $0.00008 | $0.00737 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (100 stars, last pushed 3d 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.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
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
issue-deduplicate
Merge two tracking issues that describe the same root-cause vulnerability, preserving every reporter's credit, every mailing-list thread reference, and every independent attack-vector description. Updates the kept issue's body in place, closes the duplicate with the duplicate label, and regenerates the CVE JSON…
opik-explain
Root-cause a specific Opik trace, or a pattern across traces, and return a grounded explanation. Uses the hosted Opik MCP when it is connected, and falls back to SDK scripting otherwise. Returns the root cause, the evidence spans as clickable Opik UI links, and one suggested next step. Use for "why did this trace…
audit-finding-fix
For a batch of findings from a non-security audit tool ( — ruff / flake8 / mypy / pylint / CodeQL / Apache Verum / Apache Caer / equivalent; full list in the body) against , draft the smallest fix per finding, re-running the tool after each batch to confirm clearance. Produces a commit and a hand-back artefact; never…
reproducer
For a single issue identifying a code-level bug, extract the reporter's example code from the issue body, adapt it to run on the current , execute via , and compose a verdict.json describing the observed behaviour vs the expected failure. Read-only on the tracker — produces evidence, never posts. Invoked by…
upstream-fix
Turn a framework defect the agent hit while running a Magpie skill into a fix PR against apache/magpie, one PR per defect. Confirms it is a framework bug rather than local misconfiguration or a stale snapshot, then searches for an existing issue or PR and points at that instead of opening a duplicate.