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/kairyou/agent-tools/at-commitnpx skills add kairyou/agent-tools --skill at-commitgit clone --depth 1 https://github.com/kairyou/agent-toolsWhat 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.00033 | $0.01318 |
| Opus 5 | $0.00016 | $0.00659 |
| Sonnet 5 | $0.00007 | $0.00264 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
at-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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Message Generator
Workflow
- Run
git diff --stagedto inspect staged changes. If it is empty, tell the user to rungit addfirst and stop. - Determine the description language using the Language Policy below.
- Generate the message(s) and show them for confirmation; do not commit immediately. When more than one framing is reasonable, present them as a short numbered list (
1),2), …) so the user can pick by replying with just the number. A single clear message may be shown on its own. The user may also reply with an edit or their own wording. - Run
git commit -monly after the user picks or explicitly confirms — a number from the list, "commit", or "ok" all count. Do not rungit pushunless the user explicitly asks.
Language Policy
Use this priority order for the human-readable description after type(scope)::
- Use the language explicitly requested by the user in this turn.
- Otherwise use the repository preference in
.agent-tools/config.jsonc, if it definesat-commit.language. - Otherwise use the global preference in
~/.agent-tools/config.jsonc, if it definesat-commit.language. - Otherwise use the language of the user's actual invocation text when it contains a clear, independent natural-language request. Ignore injected skill instructions, quoted or pasted content, code blocks, diffs, and tool output.
- Otherwise match the dominant language in recent repository commit subjects.
- If no dominant language is clear, default to English.
Apply this order literally and stop at the first match. Check items 2 and 3 before item 4. A bare slash command or skill invocation has no language; continue to item 5. Inspect at most the latest 20 subjects.
Keep Conventional Commits syntax tokens untranslated: type, optional scope, !, and BREAKING CHANGE. Keep identifiers, file names, package names, commands, API names, and scopes in their original language.
Persistent Language Preference
Do not write config during ordinary commit generation. If the user explicitly asks to remember a commit-description language, offer to persist it. Ask repo vs global when scope is ambiguous.
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 · 79 lines · 33 tokens per session scan A b7761adc3956
at-commit is a skill published in the GitHub repository kairyou/agent-tools (172 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 1,318 once invoked, about $0.0002 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
autopilot
Full autonomous execution from idea to working code.
deep-interview
Socratic deep interview with mathematical ambiguity gating before explicit execution approval.
plannotator-annotate
Open Plannotator's annotation UI for a file, folder, or URL, then address the returned annotations.
statistical-power
Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers…
review-work
Post-implementation review orchestrator. Launches 5 parallel background sub-agents: Oracle (goal/constraint verification), Oracle (code quality), Oracle (security), unspecified-high (hands-on QA execution), unspecified-high (context mining from GitHub/git/Slack/Notion). All must pass for review to pass. MUST USE…
southwest
Search Southwest Airlines fares and points pricing via Patchright browser automation. SW is not in any GDS or API. Covers all fare classes, Companion Pass value, and fare drop monitoring.