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-status/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-status)<a href="https://agentmods.dev/skills/vmihalis/hacker-bob/bob-status"><img src="https://agentmods.dev/badge/skills/vmihalis/hacker-bob/bob-status.svg" alt="Measured on agentmods" 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.00020 | $0.01687 |
| Opus 5 | $0.00010 | $0.00843 |
| Sonnet 5 | $0.00004 | $0.00337 |
| Haiku 4.5 | $0.00002 | $0.00169 |
Grade A, and why
bob-status 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 7d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Bob's read-only session status command. Give the operator a compact answer about where a Hacker Bob run stands and what command to run next. This is not a debug review.
Input: $ARGUMENTS (--last, no args, or <target_domain>)
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
Task. - Do not inspect Claude transcripts. Use
/bob-debug --deepfor transcript-backed root-cause analysis. - Keep the final answer short enough to read at a glance.
Argument Handling
- No args or
--last: inspect the latest local session under~/hacker-bob-sessions. <target_domain>: inspect that specific session directory.- 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.
Read Order
First, read the passive update cache if the helper is installed:
node "${CLAUDE_PROJECT_DIR:-$PWD}/.claude/hooks/bob-update.js" status "${CLAUDE_PROJECT_DIR:-$PWD}" --json
This command must only read the local update cache. Do not run network update checks from /bob-status.
After resolving target_domain, call:
bob_read_pipeline_analytics({ target_domain, include_events: false, limit: 20 })
bob_read_session_summary({ target_domain })
bob_read_state_summary({ target_domain })
bob_wave_status({ target_domain })
bob_read_verification_context({ target_domain })
If a read returns an authority error, report it as a session-integrity blocker.
Do not treat the supplied target_domain as sufficient authority, and do not
inspect or repair raw state.json; session-bound MCP tools must authorize
against the initialized session record. Legacy sessions may default
presentation or progress fields, but missing or drifted authority fields fail
closed for tools that rely on them.
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.
- 7d ago First seen · 108 lines · 20 tokens per session scan A 5555a409fa15
bob-status is a skill published in the GitHub repository vmihalis/hacker-bob (97 stars, last pushed 8d ago), licensed Apache-2.0. It adds 20 tokens to every session and 1,687 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
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…
scan-full
Comprehensive scan covering project dependencies PLUS OS/system packages (Homebrew on macOS, apt/dnf on Linux) PLUS installed IDE extensions (VS Code marketplace + JetBrains plugins). Most other supply-chain scanners only check project manifests and miss system + IDE surfaces. Use whenever the user asks for "complete…
scan
Full project dependency scan with live advisory fetch (OSV, NVD, GHSA) and EPSS exploit-probability + CISA KEV prioritisation. Covers npm and PyPI manifests + lockfiles. Use when the user wants thorough, up-to-date supply-chain CVE coverage for their project — but does NOT need system packages or IDE extensions (for…
supply-chain-scan
Scan a workspace for supply-chain CVEs across project dependencies, system packages (Homebrew/apt), and IDE extensions (VS Code, JetBrains). Findings ranked by EPSS exploit probability and CISA KEV presence — not just CVSS severity. Use when the user asks about supply-chain risk, dependency vulnerabilities, or wants…
validate-fixes
Re-scan after a dependency upgrade and confirm the CVEs are actually resolved. Use when the user has just run npm update, pip install -U, applied a patch, or otherwise upgraded packages and wants verification. Diffs a baseline scan against the post-patch scan and reports resolvedcount, remainingcount, newcount, and…
why
Explain why a specific vulnerable package is in the project — direct vs transitive dependency, which CVE IDs apply, EPSS exploit-probability score, whether it's on the CISA KEV catalog, and the recommended fix command. Use when the user asks "why is X vulnerable", "where does X come from", or "is X actually…