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-retrogit 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-retro)<a href="https://agentmods.dev/skills/codeaholicguy/ai-devkit/dev-retro"><img src="https://agentmods.dev/badge/skills/codeaholicguy/ai-devkit/dev-retro/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-retro"><img src="https://agentmods.dev/badge/skills/codeaholicguy/ai-devkit/dev-retro.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00067 | $0.00547 |
| Opus 5.5 | $0.00027 | $0.00219 |
| Sonnet 5.5 | $0.00013 | $0.00109 |
| Haiku 4.5 | $0.00007 | $0.00055 |
Grade A, and why
dev-retro 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.
What it actually says
Retro
Turn what went wrong into fixes that stop it recurring. Not a status summary: use session-compact for handoff state.
Rules
- When suggested by another skill, ask the user before running; skip silently if declined.
- Every item needs evidence: a failed command, hook or test output, a user correction, a revert, or rework in the diff. No generic lessons.
- Cap at the 3-5 highest-cost items. Note what worked in one line only if it should be kept on purpose.
- Blameless: describe the gap in the system, not the person or agent.
- Never copy secrets, credentials, or personal data from transcripts into fixes or memory.
Fix Ladder
Pick the highest rung that works:
- Automate: test, lint rule, hook, CI check, build dependency.
- Fix the tool: script, template, default config.
- Instruct: skill,
AGENTS.md/CLAUDE.md, docs. - Remember:
memoryentry, only for knowledge that cannot be enforced. Search first; update instead of duplicating. - Drop: one-off with no pattern.
Workflow
- Scope the work: feature, branch, session, or incident, and its commit range.
- Gather evidence:
git logand diff for the range, failed or retried commands, hook/CI failures,taskevidence, user corrections. Use the session transcript when available (agent sessions,session-compact); do not require it. - For each item, record: what happened, cost (time, rework, risk), root cause in one line, and the fix with its rung, exact file or command.
- Present the items and wait for approval. Memory-only fixes may proceed; skill, config, CI, and code changes need explicit approval.
- Apply approved fixes, validate each with
verify(a new check must fail on the old state when practical), and commit per the user's workflow. - Report: fixes applied with rung, items dropped and why, follow-ups left open.
Stop
Pause when evidence is missing, a fix needs a team or ownership decision, or the root cause is unclear; hand unclear failures to dev-debug.
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 · 40 lines · 67 tokens per session scan A c12d5650867d
dev-retro is a skill published in the GitHub repository codeaholicguy/ai-devkit (1,654 stars, last pushed 2d ago), licensed Apache-2.0. It adds 67 tokens to every session and 547 once invoked, about $0.0003 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-10-24.
Other skills, from other repositories
alumni-re-hire-tracker
Alumni and re-hire register: former role, last working day, re-hire eligibility, current employer and re-engagement date, as CSV, SQL, JSON Schema or Notion on request. Use for alumni outreach.
agentflow
Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and recoverable pipeline design.
asana-automation
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
conductor-status
Display project status, active tracks, and next actions.