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 skills add tutur3u/platform --skill tuturuuu-commitgit clone --depth 1 https://github.com/tutur3u/platformWrote 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/tutur3u/platform/tuturuuu-commit)<a href="https://agentmods.dev/skills/tutur3u/platform/tuturuuu-commit"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/tuturuuu-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/tutur3u/platform/tuturuuu-commit"><img src="https://agentmods.dev/badge/skills/tutur3u/platform/tuturuuu-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 37 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 70 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00019 | $0.00912 |
| Opus 5.5 | $0.00008 | $0.00365 |
| Sonnet 5.5 | $0.00004 | $0.00182 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
tuturuuu-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 3d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tuturuuu Commit
Core Workflow
Use this skill when the user explicitly asks for commits, scoped commits, atomic commits, commit-and-push follow-through, or commit reporting. Also use it to close finished authorized repository work without a separate commit prompt, under the completion contract.
Read references/commit-workflow.md for examples of scope grouping, staging,
and failure handling before creating commits.
Guardrails
- Run
git status --shortbefore staging. - Treat unknown dirty and untracked files as user-owned or other-agent-owned.
- Claim the commit window with
bun git-commit-window claimimmediately before changing the staged set or committing in a shared checkout. Usebun git-commit-window waitwhen another agent owns the window and waiting is appropriate. - Keep the commit window tight: claims default to 10 minutes, only accept 5-10-minute TTLs, and should be released as soon as commit work finishes or aborts.
- Stage only files intentionally changed for the current commit.
- Avoid
git add .in shared worktrees. - Treat existing staged files as owned by the staging agent or coordinator until
explicitly reassigned. If a path is
MM, review both staged and unstaged portions with the relevant owner before committing. - Keep commits atomic by product domain, package, behavior, or independently revertible operational policy.
- Use Conventional Commit subjects that match repo rules.
- Never include secrets, local-only scratch files, or unrelated formatting churn.
- Finished authorized work is committed and pushed to main or the appropriate authorized branch under the completion contract. Honor explicit publication holds, branch protection and review/release gates; never infer merge or production permission from push authorization.
- Let commit hooks run by default. Use
git commit --no-verifyonly when the current agent has proof-gated no-verify evidence for its exact staged paths. Do not use no-verify to bypass failures caused by unrelated worker files unless you own the staged set and have exact-path proof.
What ships with it
2 files 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.
- 3d ago Changed · +5 lines fac240498ca2
- 1mo ago Changed · -41 tokens per session 76343bad4954
- 1mo ago First seen · 90 lines · 60 tokens per session scan A 84430a5b9be2
tuturuuu-commit is a skill published in the GitHub repository tutur3u/platform (55 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 912 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
commit
Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'.
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
review-triage-phase
Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.
multiline-commit-messages
Use single-quoted strings for multiline git commit messages in the Shell tool. Prevents heredoc escaping failures that produce garbled commit messages.