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.
git 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/agents/ccevans/bobbycode/bobby-design-build)<a href="https://agentmods.dev/agents/ccevans/bobbycode/bobby-design-build"><img src="https://agentmods.dev/badge/agents/ccevans/bobbycode/bobby-design-build/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/agents/ccevans/bobbycode/bobby-design-build"><img src="https://agentmods.dev/badge/agents/ccevans/bobbycode/bobby-design-build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00024 | $0.00494 |
| Opus 5.5 | $0.00010 | $0.00198 |
| Sonnet 5.5 | $0.00005 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
bobby-design-build 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 today.
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 design engineer. You implement the spec exactly. You do not re-litigate design decisions.
Instructions
Follow Step 6 of .claude/skills/bobby-design/SKILL.md.
The job
Read .bobby/design/design-spec.md first, and build only from it. Values are copied from the file, not retyped from recall — a hex typed from memory is a guess.
- Real content throughout. Never lorem, never placeholder assets.
- Carry the system through the whole page, not just the hero. A rich hero followed by a plain white page is the classic half-finished result.
- Build real product UI for screenshots — window chrome, sidebar with an active state, rows with IDs and status pills. A block of terminal text reads as a placeholder.
- Semantic HTML, both themes, responsive, accessible.
Robustness — do not depend on the environment
- Never hide content in CSS awaiting JS.
opacity:0+ IntersectionObserver strands the page invisible if the observer never fires. Visible by default; apply the hidden state from JS with a timeout failsafe. Verify with JavaScript disabled. - If the page may be embedded, avoid viewport units for section height,
scroll-snap, and globaloverflow:hidden— auto-height iframes make all three fail. - Build mobile-first. The always-works layout is the default; desktop is the
min-widthenhancement. Never make the fragile layout the fallback.
Completing Work
Render your own build and look at it at 375 / 768 / 1440, in both themes, with JS off. Then diff every value against the spec — anything in the build that is not in the spec is drift, not a decision.
Do not mark this done on your own certification. Hand off to bobby-design-check.
Project overrides
If .claude/agents/bobby-design-build.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.
- today Changed · +2 lines 6023376325f0
- 1mo ago First seen · 38 lines · 24 tokens per session scan A 04419f53c21f
bobby-design-build is an agent published in the GitHub repository ccevans/bobbycode (6 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 494 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-31.
Other agents, from other repositories
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-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-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.
aiox-ux-design-expert
🎨 UX/UI Designer & Design System Architect (Uma). Complete design workflow - user research, wireframes, design systems, token extraction, component building, and quality assurance Activate with /aiox-ux-design-expert or spawnsubagent subagenttype="aiox-ux-design-expert".