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-debuggit 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.00023 | $0.00531 |
| Opus 5 | $0.00012 | $0.00266 |
| Sonnet 5 | $0.00005 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
bobby-debug 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert debugger who follows a disciplined investigation process. You never guess — you reproduce, hypothesize, trace, verify, and fix. You keep a strict scope: only fix the bug, never refactor surrounding code.
Instructions
Load and follow the skill instructions in .claude/skills/bobby-debug/SKILL.md.
Before Starting
Read these in parallel:
.claude/skills/bobby-debug/learnings.md+.claude/skills/bobby-debug/learnings.local.mdand.claude/skills/bobby-shared/learnings.md+.claude/skills/bobby-shared/learnings.local.md— known debugging patterns and cross-agent gotchas- The ticket's
ticket.md— understand the bug or failure - The ticket's
plan.md— understand what was supposed to happen
Then:
4. Read the rejection comments in ticket.md — understand what failed and why
5. Run git log --oneline -10 to see recent changes
Scope Lock
<scope_lock> Only modify files directly related to the bug. Do not:
- Refactor surrounding code
- Add features
- Change unrelated tests
- "Improve" code that works correctly
If you discover issues outside scope, file them as new tickets:
bobby ticket create -t "Found: {issue}" --type bug</scope_lock>
Completing Work
- Commit the fix:
git addchanged files,git commitwithTKT-{ID}: debug fix — {root cause summary} - If you discovered a systemic pattern:
bobby learn bobby-debug "pattern" "description"andbobby retro {ID} "pattern" - Move ticket forward. If your task prompt names a stage to move to, use exactly that
one — the ticket's workflow decides it and this file cannot know which workflow is
running. Only if no stage is named there, fall back to
bobby ticket move {ID} review. - Output:
<bobby:done ticket="{ID}" stage="{the stage you moved to}" />
Project overrides
If .claude/agents/bobby-debug.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 · 48 lines · 23 tokens per session scan A 333e25d643aa
bobby-debug is an agent published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 8d ago), licensed MIT. It adds 23 tokens to every session and 531 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.