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 Benknightdark/neo-skills --skill neo-stop-slopgit clone --depth 1 https://github.com/Benknightdark/neo-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/benknightdark/neo-skills/neo-stop-slop)<a href="https://agentmods.dev/skills/benknightdark/neo-skills/neo-stop-slop"><img src="https://agentmods.dev/badge/skills/benknightdark/neo-skills/neo-stop-slop/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/benknightdark/neo-skills/neo-stop-slop"><img src="https://agentmods.dev/badge/skills/benknightdark/neo-skills/neo-stop-slop.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.00080 | $0.02108 |
| Opus 5 | $0.00040 | $0.01054 |
| Sonnet 5 | $0.00016 | $0.00422 |
| Haiku 4.5 | $0.00008 | $0.00211 |
Grade A, and why
neo-stop-slop 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 12d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Neo Stop Slop
neo-stop-slop is a writing skill for removing AI tells, filler, and formulaic verbosity from Chinese and English prose. It handles copy, technical drafts, code comments, Git commits, PR descriptions, and rough notes or source material that need to become clear, accurate articles.
It combines two core workflows: Reviewer for diagnosing text and Generator for rewriting it. Article Rewrite rules add source fidelity and Taiwan Traditional Chinese writing guidance where needed.
Gotchas
- Over-shortening risk: When rewriting, preserve all important technical details and facts. Removing AI tells means removing filler and decorative structure, not deleting substance.
- Article Rewrite fact boundary: When handling drafts, notes, articles, or source material, use only information supplied and supported by the user. Do not add external context, data, causality, motives, impact, or unverified conclusions. Preserve uncertainty, attribution, and contradictions. See
references/article-rewrite.mdfor the complete rules. - Code syntax and comment markers: When trimming code comments, do not break XML documentation structures such as C#
<summary>and<param>, or JSDoc/TSDoc markers. - Analyzer execution: Run
analyze-slop.jsnon-interactively with--fileor--input, optionally using--format json; never invoke a TTY prompt that could hang the agent.
Workflow Checklist
Progress:
- Step 1 — Perceive: Identify the language, content context, and output goal. Route the request to
Review, generalRewrite, orArticle Rewrite. - Step 2 — Reason: Load only the
references/resources relevant to the context. Article Rewrite must loadarticle-rewrite.md. - Step 3 — Act: Review: Run
analyze-slop.jsonly when the user asks for an AI-tell diagnosis. - Step 4 — Act: Rewrite: Remove information-free filler, formulaic structures, and vague wording. In Article Rewrite mode, reorder the supplied information without deleting facts for brevity.
- Step 5 — Verify: Check style, source fidelity, output format, and technical markers according to the selected mode. Treat analyzer scores as diagnostic signals, not hard gates for every mode.
What ships with it
9 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.
- 12d ago First seen · 158 lines · 80 tokens per session scan A 4a2d1f976da8
neo-stop-slop is a skill published in the GitHub repository Benknightdark/neo-skills (7 stars, last pushed 6d ago), licensed MIT. It adds 80 tokens to every session and 2,108 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
html-portal-generator
Convert a codebase into a self-contained HTML portal app for ingestion into AI application systems. Produces a single deployable HTML file with embedded CSS, JS, and data.
api-designer
Design RESTful APIs with best practices for consistency and usability.
coding-assistant
Provides coding assistance with best practices and code review.
debug-helper
Systematic debugging approach for identifying and fixing issues.
git-workflow
Git best practices for version control and collaboration.
test-writer
Write thorough tests following TDD and BDD principles.