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/tutur3u/platform/tuturuuu-commitnpx 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.svg" alt="Measured on agentmods" 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 | $0.00060 | $0.00866 |
| Opus 5 | $0.00030 | $0.00433 |
| Sonnet 5 | $0.00012 | $0.00173 |
| Haiku 4.5 | $0.00006 | $0.00087 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 90 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.
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.
- Do not push unless the user explicitly asks for push.
- 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.
Commit Planning
Before staging, group changed paths by the reason they should be reverted together. Prefer a small number of meaningful commits over file-by-file commits.
Good split boundaries:
- product behavior fixes
- user-facing feature work
- package or tooling policy changes
- docs-only follow-through for a workflow change
- plugin, skill, or agent-workflow updates
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.
- yesterday First seen · 90 lines · 60 tokens per session scan A 84430a5b9be2
tuturuuu-commit is a skill published in the GitHub repository tutur3u/platform (53 stars, last pushed yesterday), licensed Apache-2.0. It adds 60 tokens to every session and 866 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.
coss-particles
Index of all COSS UI particle examples. Use when implementing UI features to find copy-paste-ready component patterns built on coss primitives. Each particle has a description and a JSON URL for easy installation.
coss
Helps implement coss UI components correctly. Use when building UIs with coss primitives and patterns (buttons, dialogs, selects, forms, menus, tabs, segmented controls, inputs, toasts, etc.), migrating from shadcn/Radix to coss/Base UI, composing trigger-based overlays, or troubleshooting coss component behavior.…
ui-beats
Use this skill when users want to add, customize, or troubleshoot UI Beats components in React/Next.js projects. It covers component selection, shadcn registry installation from uibeats.com, the UI Beats MCP server, motion and reduced-motion handling, and integration patterns for animated sections.
docs
Documentation drift detection and sync via oma-docs. Verify mode finds broken refs in docs//.md, sync mode proposes patches for docs affected by a git diff.
commit
Generate Conventional Commits spec git commits (auto-separate by feature).