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/lifedever/skills-plugin/dev-launchernpx skills add lifedever/skills-plugin --skill dev-launchergit clone --depth 1 https://github.com/lifedever/skills-pluginWrote 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/lifedever/skills-plugin/dev-launcher)<a href="https://agentmods.dev/skills/lifedever/skills-plugin/dev-launcher"><img src="https://agentmods.dev/badge/skills/lifedever/skills-plugin/dev-launcher.svg" alt="Measured on agentmods" 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 | $0.00096 | $0.01245 |
| Opus 5 | $0.00048 | $0.00622 |
| Sonnet 5 | $0.00019 | $0.00249 |
| Haiku 4.5 | $0.00010 | $0.00125 |
Grade A, and why
dev-launcher 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 4d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Launcher
Generate a dev.sh script that starts frontend and backend together with interactive controls (restart, status, quit).
Workflow
1. Detect project structure
Scan the project root to identify:
Backend (check in order, first match wins):
pom.xml→ Maven + Spring Bootbuild.gradle/build.gradle.kts→ Gradle + Spring Bootgo.mod→ Go projectrequirements.txt/pyproject.toml→ Python project
Frontend package manager (check in order):
pnpm-lock.yaml→ pnpmyarn.lock→ yarnpackage-lock.json→ npm
Directory names: List root to find server/client dirs. Common patterns: *-server/*-client, backend/frontend, server/client, api/web.
Spring profile: Check for application-dev.yml. If exists, default to dev. Respect user-specified profile.
Frontend dev command: Read package.json scripts.dev to confirm.
2. Fill template
Read references/template.sh and replace all {{...}} placeholders.
| Placeholder | Description |
|---|---|
{{SERVER_DIR_NAME}} |
Server directory name |
{{CLIENT_DIR_NAME}} |
Client directory name |
{{SERVER_PGREP_PATTERN}} |
pgrep pattern uniquely identifying this project (abs-path fragment, not a bare common dir name) |
{{CLIENT_PGREP_PATTERN}} |
pgrep pattern uniquely identifying this project (abs-path fragment, not a bare common dir name) |
{{SERVER_START_LOG}} |
Log message for server start |
{{SERVER_START_CMD}} |
Full server start command |
{{CLIENT_START_LOG}} |
Log message for client start |
{{CLIENT_START_CMD}} |
Full client start command |
{{SERVER_EXTRA_PGREP}} |
Extra pgrep logic for Maven/Gradle, or remove line |
3. Backend variants
Maven + Spring Boot:
PATTERN: spring-boot:run.*{{DIR}}
CMD: mvn clean spring-boot:run -P{{PROFILE}} -Dspring-boot.run.profiles={{PROFILE}} -Dspring.output.ansi.enabled=ALWAYS
EXTRA_PGREP: local mvn_pids=$(pgrep -f "maven.*{{DIR}}" 2>/dev/null)
pids=$(echo -e "${pids}\n${mvn_pids}" | sort -u | grep -v '^$')
What ships with it
1 file 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.
- 4d ago First seen · 94 lines · 96 tokens per session scan A aa526cd67d4f
dev-launcher is a skill published in the GitHub repository lifedever/skills-plugin (11 stars, last pushed 12d ago), licensed MIT. It adds 96 tokens to every session and 1,245 once invoked, about $0.0005 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…