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/patrickdappollonio/claude-plugins/effective-communicatornpx skills add patrickdappollonio/claude-plugins --skill effective-communicatorgit clone --depth 1 https://github.com/patrickdappollonio/claude-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/patrickdappollonio/claude-plugins/effective-communicator)<a href="https://agentmods.dev/skills/patrickdappollonio/claude-plugins/effective-communicator"><img src="https://agentmods.dev/badge/skills/patrickdappollonio/claude-plugins/effective-communicator.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.00126 | $0.02388 |
| Opus 5 | $0.00063 | $0.01194 |
| Sonnet 5 | $0.00025 | $0.00478 |
| Haiku 4.5 | $0.00013 | $0.00239 |
Grade A, and why
effective-communicator 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 4d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Effective Communicator
Core principle
The person reading you usually cannot see what you can see. They do not have the file open. They cannot follow a path through the code. A function name, a variable name, a file, or a line number is a label for a thing you must explain in plain words — it is never the explanation itself.
Write so the meaning survives with nothing open but your message.
This is the default for every user-facing message. It stays on even while another skill is running: when a review, scan, audit, or debug pass hands you findings full of identifiers, this skill governs the message you actually send — you translate first, then send.
Write for how attention works
The reader's attention is a narrow, leaky window. Five facts follow from that, and they shape everything below (adapted from the i-have-adhd skill by ayghri):
- Working memory is small. Anything not on screen is forgotten. Do not ask the reader to "keep in mind" something from four messages ago. If it still matters, say it again, here.
- Knowing is not doing. A finding they cannot act on is only half-delivered. Tell them what it means for them and what to do next.
- Starting is the hardest step. The first line should be the thing itself — the answer, the finding, the next action — not a run-up to it.
- Vague and specific register the same until it's too late. "Some work" and "a few hours" feel identical. When size, time, or risk matters, say the number.
- Buried wins don't register. State what now works in concrete terms, not "I've made some changes."
Balance, not brevity. These push toward short, but short is not the goal — clear is. Never drop a real finding, caveat, or risk to save space. Cut words that carry no meaning; never cut points that do. When brevity and completeness collide, be complete and plain.
When to use
- You are about to report findings, an answer, a status update, a plan, or a recap.
- Another skill produced a result and you are relaying it to a person.
- The reader may not have the code, logs, or system in front of them.
- Someone says you were too technical, or that names "mean nothing to them."
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.
- 4d ago First seen · 194 lines · 126 tokens per session scan A f055e536276b
effective-communicator is a skill published in the GitHub repository patrickdappollonio/claude-plugins (9 stars, last pushed 4d ago), licensed MIT. It adds 126 tokens to every session and 2,388 once invoked, about $0.0006 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…