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 skills add ccevans/bobbycode --skill bobby-ticket-intakegit 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/skills/ccevans/bobbycode/bobby-ticket-intake)<a href="https://agentmods.dev/skills/ccevans/bobbycode/bobby-ticket-intake"><img src="https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-ticket-intake/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/skills/ccevans/bobbycode/bobby-ticket-intake"><img src="https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-ticket-intake.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.00051 | $0.01086 |
| Opus 5.5 | $0.00020 | $0.00434 |
| Sonnet 5.5 | $0.00010 | $0.00217 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
bobby-ticket-intake 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 1mo ago.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bobby Ticket Intake Skill
Turn a PM spec into a Bobby ticket with real content in one pass. No placeholders. Workflow agents should be able to start from the ticket immediately.
When to Use
The user pastes a JIRA ticket body, a spec doc, or any PM-written description and wants it stored as a Bobby ticket.
Steps
1. Parse the pasted content
Extract the following fields from the pasted spec:
| Field | Where to look |
|---|---|
id |
Issue key from the ticket system (e.g. TKT-001, PROJ-123) — often in the title or URL. Omit if not present. |
title |
Summary line or first heading |
type |
epic if the spec spans multiple capabilities or explicitly says "Epic"; bug if it describes broken behaviour; task for infra/config; feature otherwise |
priority |
Explicit priority field, or infer: "critical" / "blocker" → critical, "high" / "must" → high, "nice to have" / "low" → low, default → medium |
area |
Match to a valid area from .bobbyrc.yml — read that file before inferring |
description |
Full body text cleaned to markdown. Preserve section headings and code examples. |
acceptance_criteria |
Checklist-style bullets, "Acceptance Criteria", "Definition of Done", or "AC" sections. Convert to - [ ] … format. |
open_questions |
Sections labelled "Open Questions", "TBD", "To Discuss", or any items marked with ?? or [TBD]. |
2. Read valid areas
Before inferring area, read .bobbyrc.yml and use its areas list. Do not hardcode area names.
3. Clarify before creating
If area or priority are genuinely ambiguous after reading the spec, ask the user. Do not guess at domain ownership — a wrong area routes the ticket to the wrong service.
You do not need to ask about anything else (title, type, description — extract and proceed).
4. Create the ticket via Bobby CLI
bobby ticket create -t "<title>" --type <type> -p <priority> --area <area>
# use --epic flag for epics
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.
- 1mo ago First seen · 116 lines · 51 tokens per session scan A f90bdba17c2a
bobby-ticket-intake is a skill published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 1,086 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
full-sdc
EXECUTE lean Full Story Development Cycle for one story: plan via CLI, run validate → develop → review (QG loop) → close with Sequence Lock, durable progress under .aiox/sdc/. Use when: full-sdc, full cycle, SDC, run story end-to-end.
wave-execute
EXECUTE a lean wave — plan story DAG + file-ownership batches via CLI, dispatch full-sdc per story, fan-in check, hand off merge to @devops. Use when: wave-execute, run wave, epic wave, parallel stories SDC.
close-story
Finalize bookkeeping for a story already completed by QA. Never changes lifecycle status. Use when: close story, close-story, story Done, /close-story.
develop-story
Implement a story (Ready → InProgress → ready for review). Runs the OSS develop task. Use when: develop story, develop, /develop-story, implement ACs.
review-story
QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, qa-gate, /review-story.