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 fatihguner/foreman --skill business-writing-for-leadersgit clone --depth 1 https://github.com/fatihguner/foremanWrote 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/fatihguner/foreman/business-writing-for-leaders)<a href="https://agentmods.dev/skills/fatihguner/foreman/business-writing-for-leaders"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/business-writing-for-leaders/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/fatihguner/foreman/business-writing-for-leaders"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/business-writing-for-leaders.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.00066 | $0.02929 |
| Opus 5 | $0.00033 | $0.01465 |
| Sonnet 5 | $0.00013 | $0.00586 |
| Haiku 4.5 | $0.00007 | $0.00293 |
Grade A, and why
business-writing-for-leaders 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 6d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.
Business Writing for Leaders
DELETE KEY. The most powerful writing tool a leader possesses is subtraction. Every unnecessary word dilutes authority. Every jargon-laden sentence signals that the writer is performing competence rather than demonstrating it. Every buried lead -- the critical information hidden in paragraph three -- is a tax on the reader's time and goodwill. Yet leaders write more words each year, to more people, through more channels, with less editing and less consideration for the person on the receiving end. The average executive sends and receives over 120 emails per day. The ones that get read, understood, and acted upon share a common trait: their authors wrote for the reader, not for themselves.
Researchers and practitioners writing across a decade of HBR publications converge on a conclusion that should embarrass anyone who has ever used the phrase "synergistic value proposition" in an email: good business writing is simple, clear, human, and structured around what the reader needs to know, not what the writer wants to say.
The Framework
Leadership writing rests on four principles. They are deceptively simple. Executing all four simultaneously, under time pressure, with multiple audiences, is considerably harder than any writing guide admits.
Principle 1: Write for the Reader
The discipline begins with a shift in orientation. Before writing a sentence, answer three questions:
- What does the reader need to know? Not what you want to tell them. What they need.
- What questions will they have? Anticipate and address them in order of likely importance.
- How much time will they give this? Assume less than you hope. Probably less than you think.
Respect for the reader's time is not a courtesy; it is a structural requirement. Put the most important information first. The reader who stops after the first paragraph should still have the essential message. The reader who continues should find supporting detail, not repetition.
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.
- 6d ago Changed · +171 lines · +66 tokens per session e55e171eedbf
- 12d ago First seen · 1 lines · 0 tokens per session scan A fc63743e5f53
business-writing-for-leaders is a skill published in the GitHub repository fatihguner/foreman (50 stars, last pushed 7d ago), licensed MIT. It adds 66 tokens to every session and 2,929 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-30.
Other skills, from other repositories
simplified-english
Write user-facing comments, plans, and documents in ASD-STE100 Simplified Technical English — short, unambiguous sentences with approved words and one meaning each — so readers understand them the first time.
novu-inbox-integration
Integrate Novu's in-app notification inbox into web applications. Supports React, Next.js, and vanilla JavaScript. Includes the Inbox component (bell icon + notification feed), composable components (Bell, Notifications, InboxContent, Preferences), headless hooks, branded theming, custom render props, multi-tenancy…
novu-design-workflow
Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state. Applies to BOTH dashboard-authored and code-first (@novu/framework) workflows. Use when planning a new workflow, deciding which channels to include…
human-cli
Reach the actual human you're working for via the human CLI (ask/approve/choose/tell) when you need a decision, approval, or notification and no one is watching this terminal right now. Use for background/autonomous/scheduled runs, risky or irreversible actions, and genuine multi-way ambiguity — not for routine…
novu-dashboard-workflows
Author step content for Novu workflows defined in the Dashboard or generated/edited via the Novu MCP. Use when filling in step controls (subject, body, editorType, headers, body, conditions) for email, in-app, sms, push, chat, delay, digest, throttle, or HTTP Request steps.
novu-manage-preferences
Configure notification preferences in Novu at the workflow and subscriber level. Set default channel preferences (email, SMS, push, chat, in-app), mark preferences as read-only or subscriber-editable, and manage subscriber-specific overrides. Use when setting up notification opt-in/opt-out, configuring per-channel…