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 Bilal140202/the-lord-of-the-skills --skill mohamedabdallah-14__unslopgit clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-skillsWrote 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/bilal140202/the-lord-of-the-skills/mohamedabdallah-14__unslop)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/mohamedabdallah-14__unslop"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/mohamedabdallah-14__unslop/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/bilal140202/the-lord-of-the-skills/mohamedabdallah-14__unslop"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/mohamedabdallah-14__unslop.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.00139 | $0.00909 |
| Opus 5 | $0.00069 | $0.00454 |
| Sonnet 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 9d 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.
This is a copy
100% identical to unslop-commit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 9d ago First seen · 104 lines · 139 tokens per session scan A eac20df58f4a
unslop-commit is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 139 tokens to every session and 909 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to unslop-commit, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
run-work
Execute a work unit end-to-end: sequence tasks by dependency, implement, test between tasks, commit, and track progress. Use to deliver a complete feature in one session. Invoked as /agiflow:run-work . Uses getworkunit, listtasks, updatetask, getworkunitprogress.
release-notes
Draft a release note section from a commit range, grouped by what the reader gets.
git-commit
Git commit message generator that creates conventional commit messages based on code changes.