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-worktreenpx skills add codeaholicguy/ai-devkit --skill dev-worktreegit 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.00049 | $0.00894 |
| Opus 5 | $0.00024 | $0.00447 |
| Sonnet 5 | $0.00010 | $0.00179 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
dev-worktree 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Worktree
Set up or resume the correct workspace before feature work. Keep this skill focused on repository context, worktree isolation, and dependency bootstrap. Do not perform requirements, design, planning, implementation, testing, or review work here.
Phase Contract
- Propose the exact workspace plan before changing branch or worktree state.
- Confirm the target branch/worktree with the user before switching contexts.
- Use
feature-<name>for branch and worktree names, where<name>is normalized kebab-case without the prefix. - Prefer a project-local worktree at
<project-root>/.worktrees/feature-<name>. - Use no-worktree mode only when the user explicitly requests it.
- Run all follow-up commands in the verified target context.
Start Feature Workspace
Use for a new feature start.
- Normalize feature name to kebab-case
<name>. - Determine the project root, the directory containing
.git. - If the user explicitly requests no worktree:
- Continue in the current repository and branch.
- Call out that branch/workspace isolation is reduced.
- Skip to dependency bootstrap.
- Otherwise use branch/worktree name
feature-<name>. - Ensure
.worktreesis listed in the project.gitignore; if not, add it. - If branch does not exist, run
git worktree add -b feature-<name> .worktrees/feature-<name>. - If branch exists and the target worktree does not, run
git worktree add .worktrees/feature-<name> feature-<name>. - If the target worktree already exists, reuse it after verifying it is clean enough for the requested work.
- Verify worktree context with
git -C .worktrees/feature-<name> branch --show-current; it must equalfeature-<name>. - Return the active workdir path for the next phase.
Resume Feature Workspace
Use when continuing an existing feature.
- Check current branch with
git branch --show-current. - Check available worktrees with
git worktree list. - Prefer
<project-root>/.worktrees/feature-<name>when it exists. - Otherwise use branch
feature-<name>in the current repository. - Include the selected target in the plan and wait for approval before switching.
- After approval, run future phase commands in the selected context.
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.
- yesterday First seen · 74 lines · 49 tokens per session scan A 108c3024bcfa
dev-worktree is a skill published in the GitHub repository codeaholicguy/ai-devkit (1,601 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 894 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".