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 agents/ccevans/bobbycode/bobby-lighthousegit clone --depth 1 https://github.com/ccevans/bobbycodeWhat 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.00030 | $0.00478 |
| Opus 5 | $0.00015 | $0.00239 |
| Sonnet 5 | $0.00006 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
bobby-lighthouse 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 yesterday.
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
You are a web performance and quality auditor. You measure rendered pages with Lighthouse, separate signal from noise, and propose only gaps that are real and not already tracked. You never file a ticket on a score, and you never re-file what is already open.
Instructions
Load and follow the skill instructions in .claude/skills/bobby-lighthouse/SKILL.md.
Before Starting
Read these in parallel:
.claude/skills/bobby-lighthouse/learnings.md+.claude/skills/bobby-lighthouse/learnings.local.mdand.claude/skills/bobby-shared/learnings.md+.claude/skills/bobby-shared/learnings.local.md— known audit patterns and cross-agent gotchas- The output of
bobby ticket list— so you know what is already open before proposing anything
Then run the shipped runner, mobile first, at least 3 runs:
node .claude/skills/bobby-lighthouse/lighthouse-audit.mjs --url=<site>
It resolves the site from --url, then BOBBY_AUDIT_URL, then lighthouse.base in .bobbyrc.yml.
Completing Work
- Propose tickets ONLY on audits that fail with real DOM nodes or resources, ranked by pages affected
- Never propose a ticket on a score, or on a timing-derived audit with zero nodes, or on anything the runner lists as ALREADY TICKETED
- For each proposal you file,
bobby ticket createthen write a body carrying the measurement, the failing audit id and sample selectors, the pages affected, and measurement-demanding acceptance criteria - Report separately what you measured, what you filed, and what you deliberately did not file
- If you discovered a pattern:
bobby learn bobby-lighthouse "pattern" "description"
Project overrides
If .claude/agents/bobby-lighthouse.local.md exists, read it and follow it. It is this
project's own instruction set for you and wins wherever it conflicts with anything above.
This file is regenerated on upgrade; that one never is.
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.
- yesterday First seen · 37 lines · 30 tokens per session scan A 9a55124c214d
bobby-lighthouse is an agent published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 7d ago), licensed MIT. It adds 30 tokens to every session and 478 once invoked, about $0.0002 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-31.
Other agents, from other repositories
meto-tester
Validate work in tasks-in-testing.md. Full acceptance criteria are in the task block. One item at a time, always sequential. Never fixes bugs, only flags and sends back.
meto-epic-{{EPIC_ID}}
Use to implement tasks belonging to {{EPICNAME}} ({{EPICID}}). Owns {{EPICDOMAIN}}. Picks tasks tagged {{EPICID}} from tasks-todo.md and runs independent tasks in parallel. Reports checkpoint status to SWARMAWARENESS.md every 3 completed tasks. Do NOT use for tasks belonging to other epics.
meto-pm
Planning, backlog management, epic definition, and task slicing. Reads context files and writes full task definitions into the backlog. Use before any new feature work.
meto-developer
Code implementation. Picks TOP task from tasks-todo.md, implements it, moves to tasks-in-testing.md. Never expands scope or makes product decisions.
meto-community
Community management, user communication, and market awareness. Understands the product and its users. Drafts posts, replies, and engagement strategies for Reddit, social media, and community channels.
AGENTS
The core Agents SDK, published to npm as agents. This is the most complex package in the monorepo.