AI DevKit is a local-first control layer that gives multiple AI coding agents shared configuration, a terminal dashboard, cross-agent messaging, local memory retrieval, and reusable engineering workflows. It is for developers and teams supervising agents such as Claude Code, Codex CLI, Gemini CLI, OpenCode, Pi, Cursor, Copilot, or Devin. The catalogue entries are composable skills and plugin components used within that agent-management system.
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 skills add codeaholicguy/ai-devkit --skill dev-prgit clone --depth 1 https://github.com/codeaholicguy/ai-devkitWrote 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/codeaholicguy/ai-devkit/dev-pr)<a href="https://agentmods.dev/skills/codeaholicguy/ai-devkit/dev-pr"><img src="https://agentmods.dev/badge/skills/codeaholicguy/ai-devkit/dev-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/codeaholicguy/ai-devkit/dev-pr"><img src="https://agentmods.dev/badge/skills/codeaholicguy/ai-devkit/dev-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00045 | $0.00578 |
| Opus 5.5 | $0.00018 | $0.00231 |
| Sonnet 5.5 | $0.00009 | $0.00116 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
dev-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 1mo 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev PR
Publish an already-reviewed branch for code review. Keep this separate from commit creation: if the branch has uncommitted changes, stop and ask the user to run the commit workflow first.
Contract
- Verify repository context with
git status -sb,git branch --show-current, andgit remote -v. - Confirm the branch is not the base branch and has committed changes to publish.
- Fetch the remote before comparing or rebasing.
- Rebase the feature branch onto the latest remote base branch before push/review.
- Resolve conflicts carefully, preserving intended behavior, then rerun relevant validation.
- Push safely. Use
--force-with-leaseonly when a rebase rewrote an already-pushed branch. - Open or update the host's review request: PR, merge request, or equivalent.
- Report review URL, branch, HEAD SHA, validation results, push mode, and risks.
Publish Workflow
- Inspect local context:
git status -sbgit branch --show-currentgit remote -v
- If uncommitted changes exist, stop. Do not stage, amend, squash, or commit in this skill.
- Identify the remote and base branch from repo conventions, upstream config, or user instruction; default to
origin/mainonly when that matches the repo. - Fetch the remote, inspect the delta, and rebase onto the remote base branch.
- If conflicts occur, inspect conflicted files and
git diff, resolve minimally, validate when useful,git add, then continue the rebase. Stop if the correct resolution is unclear. - Run relevant validation for the changed surface.
- Push:
- First push: set upstream.
- Normal update: plain push.
- Rebased already-pushed branch:
--force-with-lease.
- Open or update the review request using the host's tool/API/UI (
gh,glab, forge CLI, web UI, or project-specific workflow). - Write a concise review description. Include enough for reviewers to understand:
- Summary: what changed, why, and how.
- Validation: how it was verified.
- Risks: notable risks or "none known".
- Report:
- Review URL and state
- Branch and HEAD SHA
- Validation commands and exit codes
- Push mode, including whether
--force-with-leasewas used - Risks, follow-ups, or blockers
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.
- 1mo ago First seen · 47 lines · 45 tokens per session scan A 9bc593922afd
dev-pr is a skill published in the GitHub repository codeaholicguy/ai-devkit (1,649 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 578 once invoked, about $0.0002 per session on Opus 5.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
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
pr-review
Review open PRs two ways - default is a per-PR deep review with severity-tagged findings, inline comments, and a verdict; --survey runs a risk-tiered triage digest of what's safe to merge first.
pr-triage
First-touch triage for external pull requests - verdict, label, and a welcoming comment within minutes of open.
feedback-builder
Point Aeon at a service's /feedback endpoint - pull what agents reported (bugs, missing features), triage and cluster it, then build the best accepted request as a PR for a human to approve.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.
git-pr-workflows-pr-enhance
Improve pull request descriptions, change summaries, validation details, and review workflows. Use when preparing a pull request or making an existing proposal easier to evaluate.