Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vmihalis/hacker-bobnpx agentmods add skills/vmihalis/hacker-bob/bob-egressWrote 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-egress)<a href="https://agentmods.dev/skills/vmihalis/hacker-bob/bob-egress"><img src="https://agentmods.dev/badge/skills/vmihalis/hacker-bob/bob-egress/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-egress"><img src="https://agentmods.dev/badge/skills/vmihalis/hacker-bob/bob-egress.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.00025 | $0.00243 |
| Opus 5 | $0.00013 | $0.00121 |
| Sonnet 5 | $0.00005 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
bob-egress 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 9d 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
Hacker Bob Egress
Use this when the operator asks to list, add, test, enable, disable, or remove Hacker Bob egress profiles from Codex.
Input: $ARGUMENTS (list, add <name>, test <name>, enable <name>, disable <name>, or remove <name>)
Run from the project root:
node ./mcp/core/egress-cli.js "$PWD" $ARGUMENTS
Rules:
- If no subcommand is provided, use
list. - For
add <name>, prefer an environment variable reference such as--proxy-env BOB_EGRESS_GR_RESIDENTIAL_PROXY; do not ask the operator to paste credentials into chat. - For
remove <name>, ask the operator to confirm removal, then rerun with--yesonly after confirmation. - Report profile names, enabled status, region, description, and whether a proxy is configured. Never print proxy URLs or credentials.
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.
- 9d ago First seen · 22 lines · 25 tokens per session scan A 671961345493
bob-egress is a skill published in the GitHub repository vmihalis/hacker-bob (97 stars, last pushed 11d ago), licensed Apache-2.0. It adds 25 tokens to every session and 243 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…
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…
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…
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…
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…