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 commands/rigos0/superturtle/commitgit clone --depth 1 https://github.com/Rigos0/superturtleWhat 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.00000 | $0.00293 |
| Opus 5 | $0.00000 | $0.00147 |
| Sonnet 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 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
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.
- yesterday First seen · 30 lines · 0 tokens per session scan A 21fd3ccb35f2
commit is a command published in the GitHub repository Rigos0/superturtle (123 stars, last pushed 4mo 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
delegate-review
Run OCR in delegation mode — OCR handles file selection and rules, the host agent performs the actual review.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
speckit.archive
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.
speckit.opsmill.retrospect
Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
create-issue
Transform feature descriptions, bug reports, or improvement ideas into well-structured GitHub issues.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.