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 HECer/yoke --skill no-ai-slopgit clone --depth 1 https://github.com/HECer/yokeWrote 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/hecer/yoke/no-ai-slop)<a href="https://agentmods.dev/skills/hecer/yoke/no-ai-slop"><img src="https://agentmods.dev/badge/skills/hecer/yoke/no-ai-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/hecer/yoke/no-ai-slop"><img src="https://agentmods.dev/badge/skills/hecer/yoke/no-ai-slop.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.00056 | $0.01340 |
| Opus 5 | $0.00028 | $0.00670 |
| Sonnet 5 | $0.00011 | $0.00268 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
no-ai-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 10d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
No AI slop
Preserve the writer's point and voice while making the prose clearer and more alive. Remove observed patterns without turning distinctive writing into generic polished copy.
Choose the job
Edit (default). Make the minimum effective edit. Return the full edited draft and a short What changed section.
Detect. Name every pattern from this skill that appears, quote the affected line, and give a short fix. Do not rewrite, score the draft, or guess whether AI wrote it. Offer an edit after the report.
If no draft was provided, ask for it. Ask one audience/format question only when the answer would materially change the edit. If the goal is unclear, ask what the reader should think, feel, or do.
Editing principles
- Read the full draft first and identify its point plus the vocabulary, cadence, bluntness, humor, uncertainty, digressions, and polish level worth preserving.
- Make the minimum effective change. Fix observed patterns, errors, repetition, and unclear passages. Leave strong sentences alone.
- Keep the writer's meaning. Do not invent claims, examples, statistics, sources, or opinions.
- Lead with the point when setup adds nothing. Keep setup that adds context, tension, or character.
- Open up tangled prose without flattening its cadence. Keep clear fragments and changes in pace.
- Prefer concrete facts, mechanisms, consequences, and judgments over abstract importance.
- Use the portability test: a sentence that could move unchanged to another product or company is probably filler unless it carries a necessary general rule.
- Let facts and examples carry emphasis. Remove commentary that tells the reader what is important when the prose already shows it.
- Prefer direct verbs and active voice when they are clearer.
- Preserve useful edge, strong opinions, humor, and honest uncertainty.
- Keep the existing structure unless it hurts the piece. Report any meaningful reorganization.
- Preserve precise technical and domain terms. A word that is empty in marketing copy can still be correct in a product vocabulary. In Yoke, coding harness is an established, precise term; do not replace it merely because "harness" is often vague elsewhere.
What ships with it
1 file 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.
- 10d ago First seen · 104 lines · 56 tokens per session scan A 36a085f7db19
no-ai-slop is a skill published in the GitHub repository HECer/yoke (2 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 1,340 once invoked, about $0.0003 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
add-new-agent-support
Add a new agent (tool) support to agent-command-sync following the registry pattern.
neo4j-document-import-skill
Ingests unstructured and semi-structured documents into Neo4j as a knowledge graph. Use when chunking PDFs, HTML, plain text, or Markdown; extracting entities and relationships from text with an LLM (SimpleKGPipeline, neo4j-graphrag); loading JSON via apoc.load.json; building Document→Chunk→Entity graph structures; or…
neo4j-aura-agent-skill
Manages Neo4j Aura Agents via the v2beta1 REST API — create, list, get, update, delete, and invoke Aura agents backed by an AuraDB instance. Use when configuring Aura Agent tools (CypherTemplate, SimilaritySearch, Text2Cypher), setting system prompts, deploying agents to REST or MCP endpoints, or invoking agents with…
neo4j-graphql-skill
Build and configure a GraphQL API backed by Neo4j using @neo4j/graphql v7 (current) or v5 (LTS). Covers Neo4jGraphQL constructor, getSchema(), assertIndexesAndConstraints(), type definitions with @node, @relationship (IN/OUT/UNDIRECTED), @cypher for custom resolvers, @authorization/@authentication for JWT/JWKS…
neo4j-modeling-skill
Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with…
daily-news-report
Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports.