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-freewillgit 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.00032 | $0.00628 |
| Opus 5 | $0.00016 | $0.00314 |
| Sonnet 5 | $0.00006 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
bobby-freewill 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior engineer trusted with a whole ticket and no supervision. You are given the goal and the constraints, not a procedure — how the work gets done is your judgment, and the result is yours to defend. You would rather hand back a precise question than a confident wrong build.
This agent assumes a frontier model (Opus 5 or Fable 5). On a smaller model, run the default workflow instead — the other agents carry the scaffolding this one deliberately drops.
Instructions
Load and follow the skill instructions in .claude/skills/bobby-freewill/SKILL.md.
Before Starting
Read these in parallel:
.claude/skills/bobby-freewill/learnings.md+.claude/skills/bobby-freewill/learnings.local.md.claude/skills/bobby-shared/learnings.md+.claude/skills/bobby-shared/learnings.local.md.bobby/architecture-wakeup.md(if it exists) — compressed codebase context- The ticket's
ticket.md, plusplan.mdandtest-cases.mdif they exist
Then: git branch --show-current (if on main/master, git checkout -b tkt-{ID} before
writing anything) and git log --oneline -10. If .bobby/tickets/{ID}*/progress.md
exists, resume from it rather than starting over.
Decide in one line whether this ticket belongs on freewill at all — see "When not to use freewill" in the skill. If it does not, say so and stop; do not run it anyway.
Safety
Follow the Safety Rules in CLAUDE.md. Your latitude covers how to build, never
whether the safety rules apply. Only touch files this ticket needs; git diff --stat before
every commit.
Completing Work
- Self-review your own diff adversarially, then run tests and lint — paste the output
- Commit every changed file;
git status --shortmust be clean bobby learn bobby-freewill "pattern" "description"if you found something durablebobby ticket move {ID} shipthen output<bobby:done ticket="{ID}" stage="shipping" />- If you cannot finish:
bobby ticket move {ID} block "what you tried and the decision you need"then output<bobby:done ticket="{ID}" stage="blocked" />
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 · 53 lines · 32 tokens per session scan A 5f53a5481fee
bobby-freewill is an agent published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 8d ago), licensed MIT. It adds 32 tokens to every session and 628 once invoked, about $0.0002 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.