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/captainme-ai/lead-dev-os/create-prnpx skills add CaptainMe-AI/lead-dev-os --skill create-prgit clone --depth 1 https://github.com/CaptainMe-AI/lead-dev-osWhat 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.00070 | $0.00911 |
| Opus 5 | $0.00035 | $0.00456 |
| Sonnet 5 | $0.00014 | $0.00182 |
| Haiku 4.5 | $0.00007 | $0.00091 |
Grade A, and why
create-pr 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 2d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create GitHub Pull Request Skill
Purpose
This skill creates well-structured GitHub Pull Requests with descriptive titles and bodies that communicate WHAT the changes accomplish from a product/user perspective, not HOW they were implemented. Titles and descriptions use emojis for visual clarity.
When to Use This Skill
Use this skill when:
- The user asks to create a PR or pull request
- The user wants to submit their current branch for review
- The user says "open a PR", "create a PR", "submit for review"
Process
Step 1: Gather Context
Run these commands in parallel to understand the current state:
git status— check for uncommitted changesgit log --oneline main..HEAD— see all commits on this branch vs maingit diff main...HEAD --stat— see file-level summary of all changesgit branch --show-current— get current branch name
Step 2: Analyze Changes
- Run
git diff main...HEADto read the full diff - Identify the purpose of the changes — what does this accomplish for the user/product?
- Group changes into logical themes (e.g., new feature, UI update, backend change)
- Do NOT describe implementation details (no mention of specific functions, classes, variable names, or code patterns)
Step 3: Draft the PR
Title format:
<emoji> <Short description of WHAT changed>
Title rules:
- Under 70 characters
- Start with a relevant emoji (e.g., ✨ new feature, 🐛 bug fix, 🎨 UI change, 🔧 config, 📦 dependency, 🚀 performance, 🔒 security, ♻️ refactor, 🧪 tests, 📝 docs)
- Describe WHAT, not HOW
- Use present tense ("Add dark mode" not "Added dark mode")
Body format:
## ✨ What's New
- <emoji> <Change description from user/product perspective>
- <emoji> <Change description from user/product perspective>
## 🧪 Test Plan
- [ ] <verification step>
- [ ] <verification step>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Body rules:
- Focus on WHAT changed and WHY it matters
- Use emojis for each bullet point
- Never mention file names, function names, or implementation details in the summary
- The test plan should describe how to verify the behavior, not which test files to run
- Keep bullet points concise (one line each)
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.
- 2d ago First seen · 119 lines · 70 tokens per session scan A 71549319ccaa
create-pr is a skill published in the GitHub repository CaptainMe-AI/lead-dev-os (2 stars, last pushed 13d ago), licensed MIT. It adds 70 tokens to every session and 911 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
develop
Run /develop to build a feature, UI or backend, from an approved design, a page, component, API, service, or data slice. If something load bearing is undecided and no spec records it, it stops and routes you to /architect; otherwise it reads the spec plus AGENTS.md, builds, and advances the scope.
sync
Run /sync as the last step after a change is complete, around merge, to keep durable knowledge current. Updates root and nested AGENTS.md, reconciles the scope from repo evidence, and flags specs the change made stale. Surgical edits only: it adds lines, and rewrites single lines it owns. Never a whole section, never…
test
Run /test to write a test suite for code you just built or changed, after implementing a feature, route, or fix. Targets uncommitted changes automatically, reads test preferences.json for your framework (asks and saves it if absent), and picks the right strategy per file: happy path, edge cases, error states…
document
Run /document pr | changelog | release-note | postmortem (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
debug
Run /debug to find and fix a bug's root cause: a test failing for an unclear reason, /check verify finding a failure, or behavior being wrong. Runs a reproduce, localize, hypothesize, test, fix, verify loop, makes the minimal fix, and hands a regression test to /test. No features, no extra refactors.
check
Confirm a change before merge. /check verify drives the real app to prove behavior against the spec (every acceptance criterion met, every surface built). /check review runs a senior code review on a fresh model, one that did not write the code. Verify after /develop, review before a PR. Writes to docs/reviews/, never…