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 commands/vmihalis/hacker-bob/bob-updategit 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/commands/vmihalis/hacker-bob/bob-update)<a href="https://agentmods.dev/commands/vmihalis/hacker-bob/bob-update"><img src="https://agentmods.dev/badge/commands/vmihalis/hacker-bob/bob-update.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 | $0.00000 | $0.00200 |
| Opus 5 | $0.00000 | $0.00100 |
| Sonnet 5 | $0.00000 | $0.00040 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
bob-update 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 4d 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.
What it actually says
Run the installed Hacker Bob update workflow for this project.
- Run:
node "${CLAUDE_PROJECT_DIR:-$PWD}/.claude/hooks/bob-update.js" plan "${CLAUDE_PROJECT_DIR:-$PWD}" - If the helper says Hacker Bob is already up to date or cannot reach npm, report that result and stop.
- If an update is available or the install is legacy, ask the operator exactly:
Update now? - Only when the operator confirms, run:
npx -y hacker-bob@latest install "${CLAUDE_PROJECT_DIR:-$PWD}" - Then run:
node "${CLAUDE_PROJECT_DIR:-$PWD}/.claude/hooks/bob-update.js" clear-cache "${CLAUDE_PROJECT_DIR:-$PWD}" - Tell the operator to fully restart Claude Code in this project before continuing.
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.
- 4d ago First seen · 17 lines · 0 tokens per session scan A 27aa1327b976
bob-update is a command published in the GitHub repository vmihalis/hacker-bob (97 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 200 tokens. 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 commands, from other repositories
pentest
Recon and scan an authorized target with Sabba's security tools, then confirm findings.
audit
Security-audit a codebase with Sabba -- rank risk, find bugs, prove them.
prove-fix
Prove the current change actually works, by running it (base-fail / head-pass).
vet-skill
Vet a skill or plugin before installing it, by running it under observation.
validate-dependencies
Validate all task dependencies for issues.
validate-prd
Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality.