Borrowing it
Nothing to install: this file belongs to Rigos0/superturtle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Rigos0/superturtle/main/.claude/commands/commit.mdgit clone --depth 1 https://github.com/Rigos0/superturtleWrote 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/commands/rigos0/superturtle/commit)<a href="https://agentmods.dev/commands/rigos0/superturtle/commit"><img src="https://agentmods.dev/badge/commands/rigos0/superturtle/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/commands/rigos0/superturtle/commit"><img src="https://agentmods.dev/badge/commands/rigos0/superturtle/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.00000 | $0.00293 |
| Opus 5.5 | $0.00000 | $0.00117 |
| Sonnet 5.5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00029 |
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 2mo 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.
What it actually says
Commit current changes. User input: $ARGUMENTS
Instructions
- Run
git statusandgit diffto see all unstaged and staged changes. - Analyze the changes and group them by concern. If all changes are related, make one commit. If they touch unrelated areas, split into multiple commits.
- For each commit:
- Stage only the relevant files (
git add <specific files>, nevergit add .orgit add -A) - Write a commit message using conventional commits format:
type: message - Keep messages short and to the point — one line, no body unless truly needed
- Stage only the relevant files (
Commit types
feat:— new feature or functionalityfix:— bug fixdocs:— documentation onlystyle:— formatting, whitespace (not CSS)refactor:— code change that neither fixes a bug nor adds a featureperf:— performance improvementtest:— adding or updating testschore:— tooling, config, build, dependenciesci:— CI/CD changes
Rules
- If
$ARGUMENTScontains a message or instructions, use that to guide the commit message. - Never commit
.env, credentials, or secrets. - Never amend previous commits unless explicitly asked.
- Always end commit messages with the co-author line.
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.
- 2mo ago First seen · 30 lines · 0 tokens per session scan A 21fd3ccb35f2
commit is a command published in the GitHub repository Rigos0/superturtle (124 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 293 tokens. 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 commands, from other repositories
Checkpoint Commit
Commit changes at meaningful checkpoints throughout the workflow.
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
Checkpoint Commit
Commit changes at meaningful checkpoints throughout the workflow.
speckit.git.initialize
Initialize a Git repository with an initial commit.
commit
Please summarize your current changes, generate a commit message in English, then add and commit. Never include any AI tool or model as a Co-Author in commit messages. No Co-Authored-By lines referencing AI assistants.
commit
When you receive this command, do the following.