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-watchdoggit 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-watchdog)<a href="https://agentmods.dev/skills/ccevans/bobbycode/bobby-watchdog"><img src="https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-watchdog/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-watchdog"><img src="https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-watchdog.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.00055 | $0.00992 |
| Opus 5.5 | $0.00022 | $0.00397 |
| Sonnet 5.5 | $0.00011 | $0.00198 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
watchdog-check scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [ ] Health endpoint responds: `curl -s {production_url}/api/health` How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bobby Watchdog Skill
Post-deploy verification. Checks that production pages load, APIs respond, and no new console errors appear after deployment.
Before Starting
- Check learnings — Read
.claude/skills/bobby-watchdog/learnings.md+.claude/skills/bobby-watchdog/learnings.local.md - Read
.bobbyrc.ymlfor production config:production_url— base URL for productionwatchdog_pages— list of paths to check (default:["/"])
Watchdog Check Process
Step 1: Determine What to Check
Check these pages (in order):
- Pages listed in
watchdog_pagesconfig - If no config: homepage (
/), login page, main dashboard - Any pages specifically affected by the most recent deployment
Step 2: Health Checks
For each page, verify via browser automation:
Page Load:
- HTTP status is 200 (or expected redirect)
- Page renders within 5 seconds
- No blank/white page (check that main content container exists)
- Title tag is present and not "Error" or "500"
Console Errors:
- No JavaScript errors in console
- No failed network requests (4xx/5xx) except expected ones
- No unhandled promise rejections
Visual Verification:
- Screenshot each page for the record
- Key UI elements are present (navigation, main content, footer)
- No "loading" spinners stuck indefinitely
API Health (if applicable):
- Health endpoint responds:
curl -s {production_url}/api/health - Key API endpoints return expected status codes
Step 3: Compare to Pre-Deploy State
If previous watchdog results exist (.bobby/watchdog/last-run.json):
- Compare screenshot diffs for unexpected visual changes
- Compare console error counts (new errors = regression)
- Compare response times (>50% slower = regression)
Step 4: Record Results
Save to .bobby/watchdog/run-{YYYYMMDD-HHmmss}.json:
{
"timestamp": "ISO date",
"production_url": "https://...",
"pages": [
{
"path": "/",
"status": 200,
"load_time_ms": 850,
"console_errors": 0,
"failed_requests": 0,
"screenshot": "watchdog/screenshots/home-{timestamp}.png",
"passed": true
}
],
"overall": "passed"
}
What ships with it
2 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 · 128 lines · 55 tokens per session scan A aa53ac76e4fc
watchdog-check is a skill published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 992 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
browser-qa
Testing web apps through a real browser: reconnaissance before acting, selector discovery, state capture, console errors and screenshot evidence. Use on a web surface end to end, or to reproduce a front-end bug.
agent-browser
Use the host-side agent-browser CLI for local browser smoke tests, screenshots, snapshots, and simple UI validation against forwarded localhost URLs.
hatch3r-browser-verify
Opt-in browser verification skill — spec-run-first Playwright verification (assertions execute in the runner, agent reads only failures), axe-core a11y audits, toHaveScreenshot() regression diffs, E2E test scaffolds, and snapshot-mode exploratory driving. Default ON for UI-affecting agent invocations; disable globally…
hatch3r-qa-path
Produces a human-run manual QA test path from a PR, branch diff, or uncommitted working tree — a risk-ordered table of steps, expected results, and automated-coverage references plus a shippability sign-off. Rows are auto-proven via delegated verification sub-agents before emission, so the human walks only what…
hatch3r-a11y-audit
Runs a WCAG AA accessibility audit with findings and fixes across 7 scan categories (keyboard, contrast, ARIA, reduced motion, screen reader, high contrast, automated axe). Use when auditing and remediating accessibility.
hatch3r-qa-validation
E2E validation workflow producing a structured pass/fail report with evidence. Use when running QA validation, acceptance testing, verifying releases, or working on QA E2E validation issues.