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/codeaholicguy/ai-devkit/dev-lifecyclenpx skills add codeaholicguy/ai-devkit --skill dev-lifecyclegit clone --depth 1 https://github.com/codeaholicguy/ai-devkitWhat 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.00047 | $0.01561 |
| Opus 5 | $0.00023 | $0.00781 |
| Sonnet 5 | $0.00009 | $0.00312 |
| Haiku 4.5 | $0.00005 | $0.00156 |
Grade A, and why
dev-lifecycle 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 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.
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Lifecycle
Coordinate the phase-specific AI DevKit skills instead of running phase details directly.
Required phase skills:
dev-worktreefor feature workspace setup and resume.dev-requirementsfor phases 1-2: new requirement and requirements review.dev-designfor phase 3: design review.dev-planningfor phases 4 and 6: initial task planning and updates after implementation tasks.dev-implementationfor phases 5 and 7: execute plan and check implementation.dev-testingfor phase 8: write tests and verify coverage.dev-reviewfor phase 9: final code review.
Supporting skills:
memoryfor reusable project knowledge during clarification.tddfor implementation tasks.verifybefore completing implementation, implementation checks, testing claims, and review readiness.taskfor optional progress tracing when the task command is usable.
Startup Validation
At the beginning of every dev-lifecycle run:
- Run
npx ai-devkit@latest skill listto inspect currently installed project skills. - Confirm the listed skills include all required phase skills and supporting skills.
- If any required skill is missing, run
npx ai-devkit@latest skill add --built-into install all AI DevKit built-in skills. Then rerunnpx ai-devkit@latest skill list. - If installation fails or a required skill is still missing, stop and report the missing skill names and command output summary. Do not run a phase without its skill.
- Run
npx ai-devkit@latest lintto verify the configured AI docs structure. - If working on a specific feature, run
npx ai-devkit@latest lint --feature <name>. - If lint fails because project docs are not initialized, run
npx ai-devkit@latest init -a -e claude --built-in --yes, then rerun lint. - Probe optional task tracing availability:
- With a feature:
npx ai-devkit@latest task list --name <feature-name> --json - Without a feature:
npx ai-devkit@latest task list --json - Treat task tracing as available only if the read probe exits 0. If it fails, record task tracing as unavailable with the failed command and reason, then continue without task logging.
- Never block lifecycle work only because the task command is missing or unusable.
- With a feature:
- When working on a specific feature and task tracing is available:
- Load and follow
taskbefore executing a phase. - Initialize or show the task named after the feature, mark active work, and emit phase/progress/next/blocker/evidence events per
task. - Sequence task mutations; do not batch or parallelize mutations for the same feature.
- Load and follow
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.
- yesterday First seen · 106 lines · 47 tokens per session scan A 57a7c4a08718
dev-lifecycle is a skill published in the GitHub repository codeaholicguy/ai-devkit (1,601 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 1,561 once invoked, about $0.0002 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
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".