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 skills add vmihalis/hacker-bob --skill 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/skills/vmihalis/hacker-bob/bob-update)<a href="https://agentmods.dev/skills/vmihalis/hacker-bob/bob-update"><img src="https://agentmods.dev/badge/skills/vmihalis/hacker-bob/bob-update/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-update"><img src="https://agentmods.dev/badge/skills/vmihalis/hacker-bob/bob-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 25 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00019 | $0.00239 |
| Opus 5.5 | $0.00008 | $0.00096 |
| Sonnet 5.5 | $0.00004 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
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 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.
What it actually says
Hacker Bob Update
Use this when the operator asks to check, plan, or apply Hacker Bob updates from Codex.
Read Cache
Read the passive local cache without network access:
node -e "const update=require('./mcp/core/update-check.js'); console.log(JSON.stringify(update.readUpdateCache(process.cwd()) || null, null, 2));"
Check Latest
Run this only when the operator explicitly asks to check for updates:
node -e "const update=require('./mcp/core/update-check.js'); update.checkForUpdate(process.cwd(), { includeChangelog: true }).then((result) => console.log(update.renderUpdatePlan(result))).catch((error) => { console.error(error.message || String(error)); process.exit(1); });"
Apply Update
Ask before updating. When confirmed, run from the project root:
npx -y hacker-bob@latest install "$PWD"
After installation, tell the operator to restart Codex 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.
- 1mo ago First seen · 29 lines · 19 tokens per session scan A 7d72c5ff2cf4
bob-update is a skill published in the GitHub repository vmihalis/hacker-bob (100 stars, last pushed 3d ago), licensed Apache-2.0. It adds 19 tokens to every session and 239 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
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…
issue-import-via-forwarder
Sub-skill for reports relayed onto by a broker (the ASF security team, a disclosure platform, a SOC) rather than sent by the reporter. Detects the relay, extracts the credit and the reporter-addressing rules through the adapters in forwarders.enabled, and hands the routing back. Never mutates the tracker.
issue-invalidate
Close a tracker as invalid: label, closing comment, board archive, and — for imports — a polite-but-firm reply draft to the reporter with the team's reasoning. No reporter outreach for trackers imported from a public PR.
good-first-issue-sweep
Sweep the open backlog for issues that could be labelled as good first issues. Classifies each candidate as READY (propose the GFI label), NEAR-MISS (surface edits to make it GFI-ready), or SKIP using the G1–G7 rubric. Applies labels only after explicit maintainer confirmation.
deduplicate
Merge two open issues that describe the same root cause, preserving both reporters' context. Proposes a closing comment on the duplicate and a cross-reference comment on the kept issue. Waits for maintainer confirmation before posting anything or closing anything.
keys-sync
Add the Release Manager's public key to the project KEYS file: check it meets the ASF strength floor, draft the KEYS diff, and emit the svn (or backend) commands and keyserver reminder for the RM to run. Never holds the private key, never commits.