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 skills/ccevans/bobbycode/bobby-docsnpx skills add ccevans/bobbycode --skill bobby-docsgit 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.00053 | $0.00852 |
| Opus 5 | $0.00026 | $0.00426 |
| Sonnet 5 | $0.00011 | $0.00170 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
update-docs 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bobby Docs Skill
Updates project documentation after shipping. Keeps README, CLAUDE.md, and docs in sync with what was actually shipped.
Before Starting
- Check learnings — Read
.claude/skills/bobby-docs/learnings.md+.claude/skills/bobby-docs/learnings.local.md - Run
bobby ticket list done --sort newestto see recently shipped tickets - Run
git log --oneline -20to understand recent changes - Read current documentation files in parallel:
README.mdCLAUDE.md- Any
docs/directory if it exists CONTRIBUTING.mdif it existsCHANGELOG.mdif it exists
Documentation Update Process
Step 1: Identify What Changed
For each recently shipped ticket:
- Read the ticket's
ticket.mdandplan.mdto understand what was built - Check if the changes affect any documented features, APIs, or workflows
- List which documentation files need updates
Step 2: Update Each File
<update_rules> For each documentation file that needs changes:
README.md:
- Update feature descriptions if new features were shipped
- Update installation/setup instructions if dependencies or config changed
- Update usage examples if CLI or API interfaces changed
- Update screenshots if UI changed significantly
- Do NOT rewrite sections that are still accurate
CLAUDE.md:
- Update agent descriptions if new agents or skills were added
- Update workflow instructions if the workflow changed
- Update CLI command reference if new commands were added
- Keep the "Working Style" and "Safety Rules" sections current
CHANGELOG.md (if it exists):
- Add entries for shipped features, fixes, and improvements
- Follow the existing changelog format (Keep a Changelog, conventional, etc.)
- Group by: Added, Changed, Fixed, Removed
API docs (if they exist):
- Update endpoint documentation for new or changed endpoints
- Update request/response examples
- Update authentication/authorization docs if auth changed </update_rules>
Step 3: Verify Accuracy
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 98 lines · 53 tokens per session scan A 725ed0cf278e
update-docs is a skill published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 8d ago), licensed MIT. It adds 53 tokens to every session and 852 once invoked, about $0.0003 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 skills, from other repositories
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
haiku
When writing a haiku for this bot, follow these conventions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.