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/darrencroton/ai-agent-coder/commitnpx skills add darrencroton/ai-agent-coder --skill commitgit clone --depth 1 https://github.com/darrencroton/ai-agent-coderWhat 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.00013 | $0.00364 |
| Opus 5 | $0.00006 | $0.00182 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
commit 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.
What it actually says
Commit Message Format
- Line 1: short imperative summary (under 72 chars)
- Blank line
- Body: rationale + every new/changed/removed file with reason, grouped logically
Steps
- Run
git statusandgit diffto review all changes - Keep all staging and commit mechanics with the Developer. Reviewers are read-only and must never perform Git or GitHub mutations.
- Run the
lintskill over what is about to land, before staging:check --base HEAD(or the slice's starting commit). It sees uncommitted and untracked work, so it covers exactly what the commit will contain. Do not commit a new lint finding without either fixing it or stating why it stands. A missing linter is an uncovered gap to report, not a pass — if the repository has no linter for the changed languages, say so and continue. - Stage specific files by name — never
git add -Aorgit add . - Commit using a HEREDOC:
git commit -m "$(cat <<'EOF'
Short summary
Detailed description
Changed files:
- path/to/file: reason
EOF
)"
- Run
git rev-parse HEADimmediately after a successful commit and record/copy the exact 40-character hash from that command when any workflow asks for the commit hash. Do not infer a full hash from abbreviatedgit commitoutput. - Run
git statusto confirm success - Never use
--no-verifyand never amend — if a hook fails, fix the issue and create a new commit
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 · 33 lines · 13 tokens per session scan A 4da405cf59e8
commit is a skill published in the GitHub repository darrencroton/ai-agent-coder (2 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 364 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…