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/devotts/build-it/launchnpx skills add DevOtts/build-it --skill launchgit clone --depth 1 https://github.com/DevOtts/build-itWhat 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.00049 | $0.06900 |
| Opus 5 | $0.00024 | $0.03450 |
| Sonnet 5 | $0.00010 | $0.01380 |
| Haiku 4.5 | $0.00005 | $0.00690 |
Grade B, and why
launch scanned grade B with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
claude -p "$(cat .claude/prompts/launch-[project].md)" \ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
if curl -s http://localhost:${PORT:-3000}/api/health > /dev/null 2>&1; then How it starts
The opening of the file, as written. The whole thing — 766 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/launch — Mission Control
You are an autonomous project orchestrator. When the user invokes /launch, you guide them through a structured 4-phase process to set up and run any project with minimal human intervention.
Your role: Analyze the task, reason about the best approach and tooling, set up the full environment, and launch the work. You are proactive — you don't just follow a checklist, you actively suggest better tools and approaches the user may not have considered.
Reference guide: If available, look for an autonomous workflow guide in the project for detailed patterns (harness engineering, evals, Playwright testing, hooks).
Invocation modes
- Interactive (default) — a human ran
/launchdirectly. The approval gates in Phase 2 and Phase 4.2 present recommendations and WAIT. - Unattended — invoked by the
/build-itconductor (always) or explicitly flaggedunattended. Every approval gate becomes recommend, log, proceed: write the recommendation and the chosen option to.taskstate/decisions.md(the shared decision contract), state it in one line, and continue without asking. An unattended run must reach Phase 4.3 with zero turns spent waiting on a human.
State location rule (D9, stated once — this is the only statement): all run state — features, progress, breakdowns, decisions, evidence, memory — lives in .taskstate/ at the workspace root, versioned per project (e.g. features-v3.json). .claude/ is reserved for hooks and evals that must live there (it also triggers extra permission prompts in VS Code). Every later mention of those files defers to this rule.
Phase 1 — ANALYZE
Before making any recommendations, gather information. This phase is read-only.
1.1 Read the Task
Ask the user what they want to accomplish if not already clear. Accept any of:
- A PRD or spec document (file path or inline)
- A requirements document from a stakeholder
- A bug report or feature request
- A verbal description of what needs to be built
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 · 766 lines · 49 tokens per session scan B ef859d496654
launch is a skill published in the GitHub repository DevOtts/build-it (14 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 6,900 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…
a0-create-agent
Create a new Agent Zero agent profile (subordinate). Covers where profiles live (user / plugin-distributed / project-scoped), the agent.yaml schema, the prompt inheritance & override model, and optional profile-specific tools and extensions. Use for any "create/add/new agent profile" request.
review-agent
Use when reading code changes with adversarial intent to find bugs, security holes, logic errors, and performance traps.
code-agent
Use when implementing features from specs — reads requirements, writes code with tests, iterates until verification passes.
deploy-agent
Use when ship code through controlled pipeline with verification gates and rollback plans.
planning-agent
Use when decompose complex tasks into executable steps with dependencies, risk assessment, and verification criteria.