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 synthesisengineering/synthesis-skills --skill synthesis-executive-communicationgit clone --depth 1 https://github.com/synthesisengineering/synthesis-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/synthesisengineering/synthesis-skills/synthesis-executive-communication)<a href="https://agentmods.dev/skills/synthesisengineering/synthesis-skills/synthesis-executive-communication"><img src="https://agentmods.dev/badge/skills/synthesisengineering/synthesis-skills/synthesis-executive-communication/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/synthesisengineering/synthesis-skills/synthesis-executive-communication"><img src="https://agentmods.dev/badge/skills/synthesisengineering/synthesis-skills/synthesis-executive-communication.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.00086 | $0.02407 |
| Opus 5 | $0.00043 | $0.01203 |
| Sonnet 5 | $0.00017 | $0.00481 |
| Haiku 4.5 | $0.00009 | $0.00241 |
Grade A, and why
synthesis-executive-communication 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 11d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executive Communication for Technical Leaders
The problem
Technical leaders write in the register of their craft, and their most consequential readers do not read that register. The CEO, the business-unit president, the CFO, the peers who run revenue and legal and HR — these are the people who decide budgets, headcount, and the leader's own standing, and they absorb exactly the fraction of a report they understand.
The failure is silent. Nobody replies asking what a pull request is. Nobody admits they skimmed past the codename they didn't recognize. They just take in less, value the work less, and quietly build their picture of the technology organization from the parts that read like business. For a technology leader, the upward progress report is a career-load-bearing document, and register failure taxes it invisibly.
The deeper trap: an engineering-literate reviewer — human or AI — cannot catch this by feel. A review pass tuned to "avoid engineering weeds" still waves through staging, CI, and merged pull requests, because to a technical reader those aren't weeds. This skill exists because the bar is different in kind, not degree.
This skill was distilled from real report-revision cycles between technology leaders and the non-technical business principals they report to. In those cycles, drafts that had survived multi-reviewer adversarial passes tuned for factual grounding, political risk, and "executive value" still needed the same categories of content removed by hand, sentence after sentence. Those categories are the kill-list below.
The bar: the every-noun test
Would the business executive you are writing to understand every noun in this sentence?
Not "is this too deep." Not "is the altitude right." Every noun, checked one at a time — and a few verbs (merge, deploy, refactor, render). Jargon hides in nouns, and a sentence with one opaque noun is a sentence the reader skips.
A sentence that fails the test gets translated to its business consequence, not simplified into slightly-less-technical vocabulary. "Deployed to staging" does not become "pushed to the pre-production environment." It becomes "on the internal test site; customers see it after the next release."
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.
- 11d ago First seen · 121 lines · 86 tokens per session scan A 16dc5fe9c589
synthesis-executive-communication is a skill published in the GitHub repository synthesisengineering/synthesis-skills (18 stars, last pushed today), licensed Apache-2.0. It adds 86 tokens to every session and 2,407 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…