Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/thettwe/nyannnpx agentmods add skills/thettwe/nyann/commitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/thettwe/nyann/commit)<a href="https://agentmods.dev/skills/thettwe/nyann/commit"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/commit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/thettwe/nyann/commit"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00175 | $0.02182 |
| Opus 5.5 | $0.00070 | $0.00873 |
| Sonnet 5.5 | $0.00035 | $0.00436 |
| Haiku 4.5 | $0.00017 | $0.00218 |
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 1mo 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
commit
You are generating a commit message for the user's staged changes. Work
in phases. Never run git commit until the user has confirmed the message.
0. Drift check (quick, non-blocking)
Run bash bin/session-check.sh --flow=commit. If it produces output,
surface the line to the user verbatim. Do not block the flow.
1. Gather context
Run bin/commit.sh --target <cwd>. The script emits a JSON context object
(target, branch, on_main, convention, staged_files, summary,
diff, truncated).
Exit code handling:
0→ JSON context emitted. Check thenothing_stagedfield:nothing_staged: true→ ask the user what they want to stage (git add <paths>,git add -p, or "everything"), then re-run.- Otherwise → full context available. Continue.
2→ not a git repo. Tell the user, stop.
If on_main: true, warn the user that the block-main hook will reject
the commit. Suggest they create a feature branch via the new-branch
skill before continuing.
1.5. Pre-action guards + commit hygiene
Run both of these before generating the message — they inform scope choice and prevent obvious mistakes from reaching the commit message step:
bash bin/pre-action-guard.sh --flow commit --target <cwd> [--profile <resolved-profile.json>]
bash bin/commit-hygiene.sh --target <cwd> [--profile <resolved-profile.json>]
Guard handling (exit code)
| Exit | Meaning | Action |
|---|---|---|
| 0 | All guards passed (or only advisory warnings) | Surface any advisory message lines, continue |
| 3 | One or more critical guards failed | Surface the failing guard messages. Refuse to proceed unless the user passes --skip-guards explicitly (re-ask via AskUserQuestion). |
| 4 | One or more confirm-severity guards failed |
Surface the failures. Call AskUserQuestion: "Proceed despite the warnings?" Only continue on explicit confirm. |
Don't silently pass critical failures. The merge-conflict-markers
guard catching <<<<<<< in the staged diff is exactly the case where
"warn and continue" would let a broken merge into a commit.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 215 lines · 175 tokens per session scan A 389cc6651d1c
commit is a skill published in the GitHub repository thettwe/nyann (7 stars, last pushed 6d ago), licensed MIT. It adds 175 tokens to every session and 2,182 once invoked, about $0.0007 per session on Opus 5.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
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
genshijin-commit
A guide for writing short Git commit messages in Conventional Commits format, a shared style that labels changes such as features, fixes, tests, and documentation. It supports Japanese and English and emphasizes explaining why a change was made.
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
post-commit
Use when a code commit just landed (not wip/amend/undo) and CHANGELOG or plugin-version post-commit actions are needed.
commit-detection
Detects optimal commit type from git changes. Use when analyzing commits, determining commit type, or before committing.