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/minhthang1009/dotclaude/commitnpx skills add MinhThang1009/dotclaude --skill commitgit clone --depth 1 https://github.com/MinhThang1009/dotclaudeWhat 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.00024 | $0.01785 |
| Opus 5 | $0.00012 | $0.00892 |
| Sonnet 5 | $0.00005 | $0.00357 |
| Haiku 4.5 | $0.00002 | $0.00178 |
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 2d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Smart Commit
Purpose: create 1 Conventional Commits-compliant commit with a Vietnamese subject, English type, NO Claude attribution.
5-step process
Step 1 — Read state
!`git rev-parse --git-dir >/dev/null 2>&1 && git status --short || echo "(not a git repo — cannot commit)"`
!`git rev-parse --git-dir >/dev/null 2>&1 && git diff --stat || true`
!`git rev-parse --git-dir >/dev/null 2>&1 && git log --oneline -5 || true`
Group files into logical groups (e.g., auth files, test files, docs files). 1 commit = 1 topic.
Step 2 — Propose grouping
If multiple files span multiple topics → propose splitting commits:
I see 3 groups of changes:
src/auth/*— OAuth feature (5 files)tests/auth/*— OAuth tests (2 files)README.md,CHANGELOG.md— docsProposing 2 commits: (1+2 together), (3 separately). Agree?
If user has no special instruction → 1 commit for small/focused PRs, split for larger ones.
Step 3 — Analyze diff to choose type & scope
Read git diff --staged in detail, infer:
| Type | When to apply |
|---|---|
feat |
Adds user-visible functionality |
fix |
Fixes a bug that affects behavior |
refactor |
Code changes that do NOT change behavior |
perf |
Performance optimization |
docs |
Docs only (*.md, comments, docstrings) |
test |
Tests only |
style |
Formatting, linting (no logic changes) |
build |
Build system, dependencies |
ci |
CI/CD config |
chore |
Other miscellaneous tasks (rename files, clean comments, update lockfile) |
revert |
Revert a 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.
- 2d ago First seen · 188 lines · 24 tokens per session scan A a06b09b9ebec
commit is a skill published in the GitHub repository MinhThang1009/dotclaude (19 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 1,785 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-30.
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…