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 ccevans/bobbycode --skill bobby-lighthousegit clone --depth 1 https://github.com/ccevans/bobbycodeWrote 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/ccevans/bobbycode/bobby-lighthouse)<a href="https://agentmods.dev/skills/ccevans/bobbycode/bobby-lighthouse"><img src="https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-lighthouse/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/ccevans/bobbycode/bobby-lighthouse"><img src="https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-lighthouse.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.00098 | $0.01989 |
| Opus 5.5 | $0.00039 | $0.00796 |
| Sonnet 5.5 | $0.00020 | $0.00398 |
| Haiku 4.5 | $0.00010 | $0.00199 |
Grade A, and why
lighthouse-audit 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bobby Lighthouse Audit Skill
Reads the four Lighthouse pillars across every page template, works out which gaps are real, ranks them by how many live URLs they affect, and proposes tickets only on what nobody has filed yet.
Not to be confused with bobby audit
bobby audit scores the codebase on production readiness (security, reliability,
operability) from static source analysis. This skill audits rendered pages with a real
browser. Different subject, different mechanism. If someone asks whether the code is
production ready, they want the command, not this skill.
The shape of this skill
Measurement is already solved. This skill ships a runner:
node .claude/skills/bobby-lighthouse/lighthouse-audit.mjs --url=https://example.com
node .claude/skills/bobby-lighthouse/lighthouse-audit.mjs --desktop
node .claude/skills/bobby-lighthouse/lighthouse-audit.mjs --page=blog --runs=1
It resolves the site from --url, then BOBBY_AUDIT_URL, then lighthouse.base in
.bobbyrc.yml, and fails with instructions if none is set. It needs no install: it shells
out to npx --yes lighthouse@12.
Output: a ranked console report plus .lighthouse/four-pillar-audit-<formfactor>.json.
Your job is the judgement the runner cannot make: decide which proposals deserve a
ticket, write tickets someone can act on, and refuse to file noise.
Before Starting
- Read
.claude/skills/bobby-lighthouse/learnings.mdandlearnings.local.md. - Run
bobby ticket listso you know what is already open before proposing anything.
Step 1: Sweep, at least 3 runs
Run mobile first; it is where the gaps are. Use the default 3 runs. Never propose a ticket off a single run — a score that looks like a regression on one run routinely flattens over three.
Step 2: Decide what is a gap
<gap_rules> The runner pre-classifies. Do not override it without saying why.
Propose a ticket when an audit fails with one or more DOM nodes or resources. That is a specific assertion about a specific thing, and it does not move without a code change.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 164 lines · 98 tokens per session scan A 24a85eac3401
lighthouse-audit is a skill published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 2d ago), licensed MIT. It adds 98 tokens to every session and 1,989 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
wttr-weather
Weather via wttr.in GET (no key). Use for weather/forecast; prefer os.http.request.
engineering-principles
Practical engineering judgement: smallest change, subtract before adding, data structures before logic, idempotent operations, migrate callers then delete. Use when designing, building, or reviewing changes.
scheduling
Scheduling across time zones: confirm times in the attendee's own zone, use IANA zone names, mind DST edges, buffers and calendar etiquette. Use when booking meetings or calls with people in other zones.
aiox-devops
Activate Gage (devops) for GitHub Repository Manager & DevOps Specialist. Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized to push to remote repository.
agent-desktop
Use the built-in Computer sub-agent with agent-desktop for macOS desktop automation. Apply when a task needs application launching, accessibility snapshots, stable element refs, window focusing, semantic clicks/typing, or visual confirmation outside the browser sandbox.
docs-page-style
House style and structure for uploads.sh documentation pages — the MDX subject pages under apps/web/src/content/docs/ (and the docs.astro hub) built on DocsLayout. Use this whenever you write, restructure, trim, or review a docs page: requests like "clean up the galleries docs", "this docs page has too much prose"…