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/rikdc/ai-skills/commitnpx skills add rikdc/ai-skills --skill commitgit clone --depth 1 https://github.com/rikdc/ai-skillsWhat 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.00055 | $0.00766 |
| Opus 5 | $0.00028 | $0.00383 |
| Sonnet 5 | $0.00011 | $0.00153 |
| Haiku 4.5 | $0.00006 | $0.00077 |
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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit - Conventional Commit Messages
Creates commits with short conventional commit messages. Runs pre-commit checks and suggests splitting when the staged changes cover more than one concern.
Usage
/git-workflow:commit [--no-verify] [--help]
Workflow
- Pre-commit checks (unless
--no-verify): runmake checksif available. - Git analysis: inspect staged files and
git diffto identify the change. - Commit: write the message, then commit.
If nothing is staged, stage all modified files. If the diff covers distinct concerns, propose atomic commits before committing.
Message Rules
<type>(<scope>): <subject>
[body — only when required]
- No emoji. Not in the subject, not in the body.
- Subject: imperative mood, lower case, no trailing period, under 60 characters.
scopeis optional; include it only when it disambiguates.- Default to a subject line alone. Most commits need nothing more.
- Add a body only for information the diff cannot show: why the change was made, a breaking change, or an issue reference. Cap it at two short sentences or three bullets.
- Never restate the diff, list touched files, summarise your process, or add closing commentary.
Types
feat: new featurefix: bug fix, security fix, warning fixdocs: documentationstyle: formattingrefactor: restructuring without behaviour changeperf: performancetest: testschore: tooling, dependencies, configurationci: CI/CD
Splitting Criteria
Propose separate commits when the staged changes mix concerns, mix types (feature + fix + docs), or are large enough that one message cannot describe them accurately.
Examples
Good:
feat(auth): add session refresh endpointfix(render): release texture handles on unmountdocs: document the scanner exit codesrefactor: collapse duplicate error wrapping
With a body, where the reason is not visible in the diff:
fix(scanner): match patterns case-insensitively
Uppercase AWS keys were slipping through, reported in #212.
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 · 103 lines · 55 tokens per session scan A 47e3b3239ab0
commit is a skill published in the GitHub repository rikdc/ai-skills (2 stars, last pushed 19d ago), licensed MPL-2.0. It adds 55 tokens to every session and 766 once invoked, about $0.0003 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…