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 MohamedAbdallah-14/unslop --skill unslop-commitgit clone --depth 1 https://github.com/MohamedAbdallah-14/unslopWrote 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/mohamedabdallah-14/unslop/unslop-commit)<a href="https://agentmods.dev/skills/mohamedabdallah-14/unslop/unslop-commit"><img src="https://agentmods.dev/badge/skills/mohamedabdallah-14/unslop/unslop-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/mohamedabdallah-14/unslop/unslop-commit"><img src="https://agentmods.dev/badge/skills/mohamedabdallah-14/unslop/unslop-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00139 | $0.00909 |
| Opus 5.5 | $0.00056 | $0.00364 |
| Sonnet 5.5 | $0.00028 | $0.00182 |
| Haiku 4.5 | $0.00014 | $0.00091 |
Grade A, and why
unslop-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- unslop-commit — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unslop Commit
Purpose
Generate or rewrite commit messages so they read like a real engineer wrote them at the end of a real day. Conventional Commits format. Direct, specific, no template English. Why over what.
Trigger
/unslop-commit, /commit, "write a commit", "commit message", "humanize this commit", "de-slop this commit". Auto-trigger when the user has staged changes and asks for a commit message.
Rules
Subject line
- Format:
<type>(<scope>): <imperative summary> - Scope optional. Types:
feat,fix,chore,refactor,docs,test,perf,build,ci,revert. - Imperative mood:
add,fix,move,remove— notadded,fixes,fixing. - ≤50 chars when possible. Hard cap 72.
- No trailing period.
- Lowercase after
:unless the project capitalizes.
Body (only when subject can't carry it)
- Add for: non-obvious "why", breaking changes, migrations, security context, data integrity.
- Wrap at 72 chars. Bullets
-for two or more independent points. Single paragraph for one thought. - End with refs:
Closes #42,Refs #17. NoBREAKING CHANGE:unless truly breaking — and then write it.
Never include
- Template prefixes: "This commit...", "This change...", "We are...", "I have..."
- Marketing verbs: comprehensive, robust, enhance, leverage, seamless, holistic
- Filler adverbs: just, really, basically, simply, actually
- Restating the filename when scope already names it
- "As requested by..." (use
Co-authored-by:if you need attribution) - AI attribution unless the project requires it
- Emoji unless project convention says so
Auto-clarity (always include body)
- Breaking changes
- Security fixes
- Data migrations
- Reverts (cite the reverted commit)
Examples
Bad → good (slop subject, no body)
- Bad:
feat: implement a comprehensive, robust solution for user profile retrieval with enhanced error handling - Good:
feat(api): return profile fields the mobile client actually needs
Bad → good (vague body)
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 · 104 lines · 139 tokens per session scan A eac20df58f4a
unslop-commit is a skill published in the GitHub repository MohamedAbdallah-14/unslop (163 stars, last pushed 7d ago), licensed MIT. It adds 139 tokens to every session and 909 once invoked, about $0.0006 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-30.
Other skills, from other repositories
kanso-commit
Use when the user asks to commit changes, stage their work, write commit messages, or split the working tree into logical commits.
commit-ko
A Korean commit-message editor that removes stiff, translated-sounding wording while preserving the message's meaning, scope, and type. A commit message is the short record attached to a change in Git.
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…
re0-git
Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so git log alone tells the story. User-invoked: run it after a commit.
precommit
Pre-commit checks — lint:fix -> build -> test.
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…