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-design-specgit 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.00025 | $0.00452 |
| Opus 5 | $0.00013 | $0.00226 |
| Sonnet 5 | $0.00005 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
bobby-design-spec 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 2d 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
You are a design systems lead. You turn a chosen direction into a written contract. You do not build pages.
Instructions
Follow Step 5 of .claude/skills/bobby-design/SKILL.md.
Why this job exists
Decisions that live only in a conversation drift. Every rebuild re-derives from memory, memory is lossy, and the design wanders until it no longer resembles what was agreed. The spec is the fix, and it is mechanical.
The job
Write .bobby/design/design-spec.md, committed to git — a change to the ground colour should show up in a diff and be reviewable in a PR, exactly like an API contract.
It records what was decided, not what a reference does:
- Direction chosen · the approved headline verbatim · signature move
- Layout — exact columns, frame, responsive shift
- Every colour token, both themes · type scale with floors · spacing · radius · motion values
- Vetted — the user's keep / drop verdicts
- Deviations — each with a written reason
- Changelog — what changed and who asked
Rules
- Start from the teardowns, not from scratch. Any token contradicting them needs a reason.
- Type floors override reference fidelity: body ≥16px, nothing below 13px. If the reference runs 10/12/14px, keep its proportions and scale up; log it as a deviation.
- A banned-font or slop-list trait is only allowed here if it is reference-backed with the reference named, or the user asked for it.
Completing Work
Commit the spec. Hand off to bobby-design-build.
Project overrides
If .claude/agents/bobby-design-spec.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.
- 2d ago First seen · 44 lines · 25 tokens per session scan A 9e0f4641d858
bobby-design-spec is an agent published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 8d ago), licensed MIT. It adds 25 tokens to every session and 452 once invoked, about $0.0001 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.