bobbycode: Skill for Claude Code

.claude/skills/bobby-vet/SKILL.md

vet-idea is a skill for Claude Code from ccevans/bobbycode. It costs 60 tokens per session (1,769 once invoked), scanned A, original, MIT.

A structured review process for challenging a ticket or idea before planning begins. It asks focused questions, examines assumptions, compares alternatives, and maps decisions that depend on one another.

In plain words
What is it for?
Use it to stress-test feature proposals, ticket designs, technical approaches, and plans before committing to a solution.
Why use it?
It exposes unclear requirements and risky assumptions before they turn into implementation work.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths.

This is ccevans/bobbycode's own configuration. It tells Claude Code how to work on bobbycode itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything bobbycode configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ccevans/bobbycode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ccevans/bobbycode/main/.claude/skills/bobby-vet/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ccevans/bobbycode

Made for: Claude Code.

Wrote 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.

agentmods badge for vet-idea

README.md
[![agentmods](https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-vet/github.svg)](https://agentmods.dev/skills/ccevans/bobbycode/bobby-vet)
Your own site
<a href="https://agentmods.dev/skills/ccevans/bobbycode/bobby-vet"><img src="https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-vet/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.

agentmods 80×15 button for vet-idea

Your own site · 80×15
<a href="https://agentmods.dev/skills/ccevans/bobbycode/bobby-vet"><img src="https://agentmods.dev/badge/skills/ccevans/bobbycode/bobby-vet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,769 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00060 $0.01769
Opus 5 $0.00030 $0.00885
Sonnet 5 $0.00012 $0.00354
Haiku 4.5 $0.00006 $0.00177

Measured 5d ago against content hash 75908ae58048, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

vet-idea 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 5d 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.

.claude/skills/bobby-vet/SKILL.md · 176 lines

How it starts

The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bobby Vet Skill

Stress-tests ideas before they enter planning. Asks probing questions one at a time, challenges assumptions, explores alternatives, maps decision dependencies, and refines ticket descriptions.

Before Starting

  1. Check learnings — Read .claude/skills/bobby-vet/learnings.md + .claude/skills/bobby-vet/learnings.local.md
  2. Read the ticket (if one was provided) — title, description, acceptance criteria
  3. Read the parent epic (if parent field exists) — understand the broader feature context
  4. Scan the backlogbobby ticket list backlog to check for related or duplicate tickets

Core Methodology: Sequential Interrogation

<interrogation_rules> These rules define bobby-vet's behavior. Follow them strictly:

  1. ONE question at a time. Never ask multiple questions in a single message. Each message contains exactly one probing question, plus optionally a brief observation that motivated it.

  2. Wait for the answer. Do not proceed to the next question until the user has responded.

  3. Go deep before going wide. If an answer reveals an assumption or gap, follow that thread with 2-3 more questions before moving to a new topic.

  4. No leading questions. Ask open questions that could go multiple ways: "What happens when..." not "Don't you think we should..."

  5. Name what you're probing. Start each question with a bracketed label so the user can track the investigation: [Scope], [Users], [Edge Case], [Dependency], [Alternative], [Priority], [Risk], [Data Model], [Integration], [Migration]. </interrogation_rules>

Procedure

Phase 1: Understand (3-5 questions)

Goal: Fully understand the idea before challenging it.

Question categories:

  • [Scope] What is the core problem this solves? Who asked for it and why?
  • [Users] Who are the primary users? How do they solve this problem today?
  • [Priority] Why now? What happens if we don't build this for 6 months?
  • [Success] How will we know this worked? What metric moves?

Read the full file on GitHub · 176 lines

Files

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.

Changes

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.

  1. 5d ago First seen · 176 lines · 60 tokens per session scan A 75908ae58048

Subscribe to this mod's changes

vet-idea is a skill published in the GitHub repository ccevans/bobbycode (6 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 1,769 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-09-03.

Related

Other skills, from other repositories

ez-workflow

Use when about to run git branching, commit, push, or PR operations in a repo managed by ez-stack. Provides the complete command reference and agent-specific usage patterns.

rohoswagger/ez-stack · 38 tokens

app-store-screenshots

Use when building App Store or Google Play screenshot pages, generating exportable marketing screenshots for iOS and/or Android apps, or creating programmatic screenshot generators with Next.js. Triggers on app store, play store, screenshots, marketing assets, html-to-image, phone mockup, android screenshots, feature…

fatihkan/badi · 68 tokens

expo-app-config

Choosing between app.json vs app.config.ts vs app.config.js, environment variables, variants, extra fields, plugin chain, and slug/scheme/bundle/version discipline. Triggers on app.json, app.config.ts, app.config.js, expo config, environment variable, .env, eas secret, variant, extra field, slug, scheme, bundle…

fatihkan/badi · 86 tokens

expo-modules

Writing Swift/Kotlin native modules with the Expo Modules API, requireNativeModule, async functions, view modules, and the event-emitter pattern. Triggers on expo modules, native module, swift, kotlin, requireNativeModule, expo-module-scripts, expo.modules.json, view module, event emitter, native function, async…

fatihkan/badi · 77 tokens

expo-config-plugin

Writing Expo config plugins, withInfoPlist, withAndroidManifest, withDangerousMod, mod compose, plugin testing, and registration in app.config.ts. Triggers on config plugin, with-plugin, withInfoPlist, withAndroidManifest, withDangerousMod, withEntitlementsPlist, withGradleProperties, mod, native config, expo plugin…

fatihkan/badi · 85 tokens

expo-eas-update

Publishing OTA updates with EAS Update, channels, runtime versions, branch management, and rollback strategy. Triggers on eas update, ota, over-the-air, runtime version, channel, branch, rollback, embedded update, asset selection, expo-updates, hot update, partial release, release cohort.

fatihkan/badi · 65 tokens