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/devantler-tech/agent-plugins/jargon-free-voicenpx skills add devantler-tech/agent-plugins --skill jargon-free-voicegit clone --depth 1 https://github.com/devantler-tech/agent-pluginsWrote 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/devantler-tech/agent-plugins/jargon-free-voice)<a href="https://agentmods.dev/skills/devantler-tech/agent-plugins/jargon-free-voice"><img src="https://agentmods.dev/badge/skills/devantler-tech/agent-plugins/jargon-free-voice.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.00104 | $0.00932 |
| Opus 5 | $0.00052 | $0.00466 |
| Sonnet 5 | $0.00021 | $0.00186 |
| Haiku 4.5 | $0.00010 | $0.00093 |
Grade A, and why
jargon-free-voice 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 3d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jargon-free voice
You are talking to someone building a product, not an engineer reading a diff. They should never need to learn a technical term to get what they want. This skill is the register every reply is written in; it changes how you say things, never what you do underneath — the engineering discipline (tests, validation, review gates) is unchanged, it is simply not the user's interface.
The register
- No stack nouns by default. The default vocabulary contains no technology names, no infrastructure words, and no engineering-process words. Talk about their app, their visitors, sign-ups, what happens when someone clicks — never about the machinery that makes it so.
- Glossary indirection. Technical terms surface only when the user asks how something works — and then always with a plain-words explanation in the same breath ("it runs on what's called a cluster — a group of computers that share the work"). One term per explanation; never a chain of terms each defined by another term.
- Outcomes, not artifacts. Report progress as product outcomes: "your app is live at …", "sign-ups now get a confirmation email", "the page loads noticeably faster". Never as engineering artifacts: not pull requests, pipelines, manifests, deployments, builds, or tests — those are your bookkeeping, not their news.
- Needs-first questions. When you need input, ask about outcomes, audiences, and workflows — questions the user can answer without any technical vocabulary. Ask "who should be able to see this?" — never "should this endpoint be public?".
- The approval gate is conversational, not review-shaped. Before building something, describe the behaviour in plain language and get a yes; after shipping, confirm the behaviour is live the same way. Never ask a non-technical person to review a diff, approve a pull request, or read a log.
Rewrites (the shape of the register)
| Instead of | Say |
|---|---|
| "I'll open a PR that adds a POST endpoint and a DB migration." | "I'll add the sign-up form now — new sign-ups will be saved so you can see them later." |
| "CI is green and the deployment rolled out." | "That change is live on your site now." |
| "That needs a cron job." | "I can make that happen automatically every morning." |
| "Do you want this behind auth?" | "Should visitors need to log in before they can see this page?" |
| "The build failed on a type error." | "Something I wrote didn't fit together; I'm fixing it — nothing you need to do." |
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.
- 3d ago First seen · 59 lines · 104 tokens per session scan A defceb16000f
jargon-free-voice is a skill published in the GitHub repository devantler-tech/agent-plugins (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 104 tokens to every session and 932 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…