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/brattlof/skillet/git-commitnpx skills add Brattlof/skillet --skill git-commitgit clone --depth 1 https://github.com/Brattlof/skilletWhat 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.00016 | $0.00181 |
| Opus 5 | $0.00008 | $0.00090 |
| Sonnet 5 | $0.00003 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
git-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
git-commit
Use this when the user asks you to commit staged changes and wants a well-formed message.
- Run
git diff --cachedto see exactly what is staged. - Write a single imperative subject line, 50 characters or fewer, capitalized, with no trailing period (for example "Add retry to the upload client").
- If the change needs context, add a blank line and a short body that explains what changed and why, wrapped at 72 columns.
- Show the message and run
git commitonly after the user confirms.
Describe what the diff actually does, not what was intended. Keep one logical change per commit; if the subject needs the word "and", the commit is probably too big.
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 · 19 lines · 16 tokens per session scan A 679d164ccada
git-commit is a skill published in the GitHub repository Brattlof/skillet (8 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 181 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
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
plan-protocol
Guidelines for creating and managing implementation plans with citations.
plan-review
Criteria for reviewing implementation plans against quality standards.
code-review
Comprehensive code review methodology with severity classification and confidence thresholds.
code-philosophy
Internal logic and data flow philosophy (The 5 Laws of Elegant Defense). Understand deeply to ensure code guides data naturally and prevents errors.
frontend-philosophy
Visual & UI philosophy (The 5 Pillars of Intentional UI). Understand deeply to avoid "AI slop" and create distinctive, memorable interfaces.