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 agentmods add skills/global-mindee/way/dumbifynpx skills add Global-mindee/WAY --skill dumbifygit clone --depth 1 https://github.com/Global-mindee/WAYWrote 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/global-mindee/way/dumbify)<a href="https://agentmods.dev/skills/global-mindee/way/dumbify"><img src="https://agentmods.dev/badge/skills/global-mindee/way/dumbify.svg" alt="Measured on agentmods" 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 | $0.00084 | $0.01132 |
| Opus 5 | $0.00042 | $0.00566 |
| Sonnet 5 | $0.00017 | $0.00226 |
| Haiku 4.5 | $0.00008 | $0.00113 |
Grade A, and why
dumbify 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 today.
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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dumbify
People don't churn because content is too simple. They churn because following it is too much work. Every bit of mental effort — a fancy word, a nested sentence, undefined jargon — is a reason to swipe away. This skill cuts that effort.
Target: ~8th-grade reading level for the body, ~6th for hooks. Easy to follow = low strain = high retention.
Simple language, not simple ideas
You are lowering the reading level, not dumbing down the thinking. The idea can be sophisticated; the words shouldn't be. Simple ≠ simplistic. A sharp 13-year-old should be able to follow it — that doesn't mean the insight is for 13-year-olds.
Where it earns its keep
- High value: explainers, educational/teaching content, how-to, anything on a technical, financial, or abstract topic. This is where dense writing kills retention.
- Low value: already-conversational captions, short hooks, casual personal stories — these come out simple naturally. Don't force this skill where there's nothing to simplify.
The moves
- Cut jargon — or swap it for the word you'd use telling a friend who isn't in the field. (Jargon the audience shares is fine — it's only friction when they don't have it. If you have an audience profile, respect the jargon they already know; a technical audience keeps its technical words.)
- One idea per sentence — break nested clauses into separate sentences.
- Common words over fancy ones — use not utilize, help not facilitate, show not demonstrate, enough not sufficient, about not approximately.
- Concrete over abstract — "the export button" not "the relevant control"; "you'll save 2 hours" not "efficiency gains."
- Active voice — "the model picks the next word," not "the next word is selected by the model."
- Cut filler that adds no meaning — "basically," "in order to," "the fact that."
- Teach by example — one concrete example lowers load more than a precise definition. Show it happening.
What ships with it
2 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.
- today First seen · 64 lines · 84 tokens per session scan A 830e17a33b48
dumbify is a skill published in the GitHub repository Global-mindee/WAY (11 stars, last pushed 1mo ago), licensed MIT. It adds 84 tokens to every session and 1,132 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-09-03.
Other skills, from other repositories
pwn-ai-agent-curriculum
Drive PWN::AI::Agent::Curriculum from pwneval.
Teach
Interactive voice-narrated tutorial on whatever the current conversation is about — teaches the topic beat by beat with ASCII diagrams in the terminal while speaking the actual lesson content aloud, asking one question per beat and quizzing until the ideas land. USE WHEN teach me, /teach-me, tutorial, teach me this…
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.