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 xbklairith/kisune --skill deslopgit clone --depth 1 https://github.com/xbklairith/kisuneWrote 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/xbklairith/kisune/deslop)<a href="https://agentmods.dev/skills/xbklairith/kisune/deslop"><img src="https://agentmods.dev/badge/skills/xbklairith/kisune/deslop/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/xbklairith/kisune/deslop"><img src="https://agentmods.dev/badge/skills/xbklairith/kisune/deslop.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.00130 | $0.01545 |
| Opus 5.5 | $0.00052 | $0.00618 |
| Sonnet 5.5 | $0.00026 | $0.00309 |
| Haiku 4.5 | $0.00013 | $0.00154 |
Grade A, and why
deslop 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 8d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deslop
Rewrite prose so it reads like a person who knows the subject wrote it. Change how it says things, never what it says.
When to Use
- The user asks to tighten, clean up, de-slop or humanize text, or says it sounds like AI.
- Another skill hands over a draft to polish (a PR description, a post-mortem).
It works on any existing prose: a lesson, an explanation, research notes, a report, a README, release notes. Not for writing new text from scratch, code, or fiction and creative writing where the voice is the point.
Keep exactly
These survive a rewrite character for character:
- Identifiers, paths, flags, env vars, commands, error text, version numbers.
- Numbers, dates, names, formulas and equations, issue and PR references.
- Citations and the claim they support; the source's own hedges ("may", "in one study") are facts too.
- Requirement lines (EARS
WHEN … THEN the system SHALL …), acceptance criteria, quoted text. - Tables and lists of reference data. A list is fine when the content is a list.
Every claim in the original stays. Do not add a fact, number, cause, owner, benefit, follow-up, or a "that is why" link that the source does not state, even one you know is true. If a sentence needs a missing detail, ask or write the simpler sentence.
Rearrange
When a template or another skill fixes the structure (section order, labels, headings), keep it and change sentences only.
Order is part of meaning. Before polishing sentences, fix the order:
- Lead with the point: what changed, what to do, or the conclusion. Background after.
- Put prerequisites, warnings and version requirements before the step they govern, not in a trailing "Don't forget" note.
- Steps in the order they are run. Related facts together; one idea per paragraph.
- Split a sentence that carries two instructions.
Plain words
Use the word people in the field say and search for, not the word an LLM reaches for. "use" not "leverage", "help" not "facilitate", "faster" not "more performant", "fix" not "remediate". In Thai, use the words Thai readers in that field use, including English loanwords where they are the norm (deploy, cache, DNA, GDP), instead of coined formal Thai, and drop the formal padding listed in references/thai.md.
What ships with it
3 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.
- 8d ago First seen · 92 lines · 130 tokens per session scan A 7e8d7dac920e
deslop is a skill published in the GitHub repository xbklairith/kisune (3 stars, last pushed 8d ago), licensed MIT. It adds 130 tokens to every session and 1,545 once invoked, about $0.0005 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-10-10.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.