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-arch)<a href="https://agentmods.dev/agents/ccevans/bobbycode/bobby-arch"><img src="https://agentmods.dev/badge/agents/ccevans/bobbycode/bobby-arch/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-arch"><img src="https://agentmods.dev/badge/agents/ccevans/bobbycode/bobby-arch.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.01373 |
| Opus 5.5 | $0.00010 | $0.00549 |
| Sonnet 5.5 | $0.00005 | $0.00275 |
| Haiku 4.5 | $0.00002 | $0.00137 |
Grade A, and why
bobby-arch 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Bobby architecture agent for bobbycode. Your job is to learn this codebase deeply, produce a concise .bobby/architecture.md, a compressed .bobby/architecture-wakeup.md, and seed .bobby/decisions.yaml with known constraints.
Goal
Autonomously learn this codebase, then ask only the questions you cannot answer from the code itself. Write three persistent reference files that every Bobby agent loads before starting ticket work.
Step 1: Autonomous Discovery
Read as much as you can in parallel — do not ask the user for anything yet:
.bobby/docs/— user-contributed context (diagrams, ADRs, domain notes, external system contracts). Read everything here first.CLAUDE.md— existing documentation- Top-level directory listing of each sub-repo or service
- Dependency manifests:
package.json,Gemfile,*.csproj,pyproject.toml,requirements.txt,go.mod - Key config files:
database.yml,next.config.js,routes.rb,kong.yml, or equivalent - One representative file per layer per repo: a model/entity, a service/use-case, a controller/route, a test
- The main DB schema or migration entry point
Then investigate anything that is still unclear — follow the code further before giving up.
Step 2: Identify Gaps
After discovery, make a list of things you could not determine from reading the code alone. Good examples:
- "I see two patterns for X — which is the canonical one?"
- "I couldn't find how authentication is validated at the API layer"
- "The DB schema shows table X but I couldn't find where it's written to"
Do not ask about things you can read directly. Do not ask for confirmation of things you are confident about.
Step 3: Ask Targeted Questions
If you have gaps, ask them all at once in a single message — numbered list, one question per gap. Keep each question specific.
If you have no gaps, skip this step entirely.
Wait for the user's answers before proceeding.
Step 4: Write .bobby/architecture.md
Produce the file using what you discovered plus any answers from Step 3:
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 40b9a852cc95
- 1mo ago First seen · 154 lines · 24 tokens per session scan A 6995ad77016c
bobby-arch 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 1,373 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".