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 Kripu77/software-factory --skill unslopgit clone --depth 1 https://github.com/Kripu77/software-factoryWrote 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/kripu77/software-factory/unslop)<a href="https://agentmods.dev/skills/kripu77/software-factory/unslop"><img src="https://agentmods.dev/badge/skills/kripu77/software-factory/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/kripu77/software-factory/unslop"><img src="https://agentmods.dev/badge/skills/kripu77/software-factory/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.00014 | $0.01619 |
| Opus 5 | $0.00007 | $0.00809 |
| Sonnet 5 | $0.00003 | $0.00324 |
| Haiku 4.5 | $0.00001 | $0.00162 |
Grade A, and why
unslop 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 — 33 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unslop
Edit text to remove AI patterns and add human voice.
Process
-
Scan for the patterns below.
-
Rewrite. Preserve meaning, match intended tone.
-
Add soul (see next section).
-
Self-audit: "What makes this obviously AI generated?" Fix remaining tells.
Adding soul
Removing patterns is half the job. Sterile, voiceless writing is just as obvious.
-
Have opinions. React to facts instead of neutrally listing pros and cons.
-
Vary rhythm. Short sentences. Then longer ones that take their time. Mix it up.
-
Acknowledge complexity. "Impressive but also kind of unsettling" beats "impressive."
-
Use "I" when it fits. First person isn't unprofessional.
-
Let some mess in. Perfect structure looks machine-made.
-
Be specific. Not "this is concerning" but "there's something unsettling about agents churning away at 3am."
Patterns to detect and fix
Content
-
Puffery. "pivotal moment", "testament to", "evolving landscape", "setting the stage for", "indelible mark", "deeply rooted". Cut puffery, state what happened.
-
Name-dropping. Listing media outlets without context. Pick one, say what was said.
-
Superficial -ing phrases. "highlighting...", "ensuring...", "reflecting...", "showcasing...", "fostering...". Delete or expand with real sources.
-
Promotional language. "nestled", "vibrant", "breathtaking", "groundbreaking", "renowned", "stunning", "must-visit". Use neutral descriptions.
-
Vague attributions. "Experts believe", "Industry reports suggest", "Some critics argue". Name the source or delete.
-
Formulaic challenges. "Despite challenges... continues to thrive." Replace with specific facts.
Language
-
AI vocabulary. Additionally, crucial, delve, enduring, enhance, fostering, garner, interplay, intricate, landscape (abstract), pivotal, showcase, tapestry (abstract), testament, underscore, vibrant. Replace with plain words.
-
Fancy ways to say "is". "serves as", "stands as", "boasts", "features". Just say "is" or "has".
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 · 112 lines · 14 tokens per session scan A 363b04ea99b5
unslop is a skill published in the GitHub repository Kripu77/software-factory (6 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 1,619 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to unslop, differing in 33 lines, and is treated as a copy.
Other skills, from other repositories
link-ticket-to-session
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma. Use when the user explicitly asks to link, attach, associate, or connect this session to a ticket, issue, or PR — e.g. "/link-ticket-to-session ABC-123", "link this session to…
save
Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.
import
Import a self-contained NeatContext context bundle shared by another person, or reconcile a newer copy of a context already on this machine, leaving the source bundle unchanged. Use only when the user explicitly invokes this skill or asks to import a NeatContext bundle.
create
Create a fresh NeatContext context from a user-defined behavioral profile and an existing local knowledge folder. Use only when the user explicitly invokes this skill or asks to create a new context rather than save the current conversation.
extensions
Report which extensions the connected NeatContext context expects, and whether this machine provides them. Use when the user asks what a context can reach, why an extension tool is missing, or how to connect one here.
export
Export a NeatContext context saved from a conversation into a self-contained bundle folder that can be shared or moved to another machine. Use only when the user explicitly invokes this skill or asks to export a NeatContext context.