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 instructions/ccevans/bobbycode/claude-mdgit 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/instructions/ccevans/bobbycode/claude-md)<a href="https://agentmods.dev/instructions/ccevans/bobbycode/claude-md"><img src="https://agentmods.dev/badge/instructions/ccevans/bobbycode/claude-md.svg" alt="Measured on agentmods" 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 | $0.03719 | $0.03719 |
| Opus 5 | $0.01860 | $0.01860 |
| Sonnet 5 | $0.00744 | $0.00744 |
| Haiku 4.5 | $0.00372 | $0.00372 |
Grade C, and why
bobbycode CLAUDE.md scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- `rm -rf` or `rm -r` on directories outside the ticket's scope How it starts
The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bobbycode — Bobby Workflow
This file was generated by
bobby init. It tells Claude Code how to work with your project using Bobby's structured workflow.
Project
- Name: bobbycode
- Stack: generic
- Tickets:
.bobby/tickets/
Health Checks
Before starting work, verify the dev environment is running:
- No health checks configured. Add them to
.bobbyrc.yml.
Feature Areas
targets | dashboard | audit | tickets | packs | templates | cli
Commands
- Test:
npm test - Lint:
npm run lint
Workflow
Bobby uses a ticket-based workflow with frontmatter-based stages:
backlog → planning → building → reviewing → testing → shipping → done
Tickets live in .bobby/tickets/ — stage is tracked in ticket.md frontmatter.
Blocked tickets have blocked: true in frontmatter with a reason.
Safety Rules
<safety_rules> All agents must follow these rules. Violations are treated as critical failures.
Never run destructive commands:
rm -rforrm -ron directories outside the ticket's scopeDROP TABLE,DROP DATABASE,TRUNCATEor any destructive SQLgit push --forceorgit push -f(use--force-with-leaseif rebase is needed)git reset --hard(usegit stashorgit checkout -- <file>for targeted reverts)git clean -fdorgit clean -fxdocker system prune,docker volume rmkill -9on unknown processeschmod -R 777orchown -Ron system directories- Any command with
sudounless the plan explicitly requires it
Never modify outside your scope:
- Do not edit files unrelated to the current ticket
- Do not change CI/CD configuration unless the ticket explicitly requires it
- Do not modify environment files (.env, credentials, secrets)
- Do not install global packages or change system-level config
Always verify before acting:
- Run
git diff --statbefore committing to review what changed - Run tests before marking work complete
- Check
git statusafter every commit to confirm clean state </safety_rules>
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 · 302 lines · 3,719 tokens per session scan C a3f93dc59efb
bobbycode CLAUDE.md is an instructions file published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 10d ago), licensed MIT. It adds 3,719 tokens to every session, about $0.0186 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other instructions, from other repositories
huly-mcp AGENTS.md
Instructions for dearlordylord/huly-mcp, a project described as: Huly MCP and CLI: Feature-complete MCP server and CLI for Huly platform.
ESAA-Core AGENTS.md
Instructions for elzobrito/ESAA-Core, covering agents.md — contrato operacional codex/esaa, 1. autoridade e termos, 2. cli e runner, ou configure o runner uma vez por sessão and 3. concorrência.
idd-skill idd-resume.instructions.md
Instructions for kurone-kito/idd-skill, covering idd — resume phase, required inputs, step 0 — route classifier, operator-present release and step 1 — identify claim state.
tmetric-minimal-mcp CLAUDE.md
Claude Code instructions for guglielmo/tmetric-minimal-mcp, covering claude.md, development commands, project architecture, file structure and core architecture patterns.
shelly-forge CLAUDE.md
Claude Code instructions for mslavov/shelly-forge, covering documentation usage guidelines, critical: framework-first reading order, 📚 mandatory reading order, pre-task protocol and post-task protocol.
vibelive AGENTS.md
AGENTS.md instructions for pooriaarab/vibelive, covering agents.md, repository context, pull requests, cloud agents (cursor) and install & test.