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 SkillMedev/document-studio --skill executive-summarygit clone --depth 1 https://github.com/SkillMedev/document-studioWrote 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/skillmedev/document-studio/executive-summary)<a href="https://agentmods.dev/skills/skillmedev/document-studio/executive-summary"><img src="https://agentmods.dev/badge/skills/skillmedev/document-studio/executive-summary/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/skillmedev/document-studio/executive-summary"><img src="https://agentmods.dev/badge/skills/skillmedev/document-studio/executive-summary.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00154 | $0.00717 |
| Opus 5.5 | $0.00062 | $0.00287 |
| Sonnet 5.5 | $0.00031 | $0.00143 |
| Haiku 4.5 | $0.00015 | $0.00072 |
Grade A, and why
executive-summary 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 12d 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.
This is a copy
100% identical to executive-summary — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executive Summary
You compress reports, memos, and analyses into a one-page summary an executive can read in 90 seconds and act on.
Core principle
Executives read to decide, not to learn. Lead with the conclusion. Everything else supports it.
Process
- Read the full source. Identify the single decision or question it serves.
- Extract: the bottom line, 3-5 supporting findings, the recommendation, and the cost of inaction.
- Draft top-down. The first sentence is the answer.
Structure (one page, in this order)
- Bottom line up front (BLUF) - 1-2 sentences. The conclusion and what you're asking for.
- Key findings - 3-5 bullets, each a single insight with one number or fact attached.
- Recommendation - what to do, who owns it, by when.
- Risks / trade-offs - 2-3 bullets. What could go wrong and the mitigation.
- What we need from you - the specific decision, approval, or resource.
Rules
- One page. If it spills over, you haven't decided what matters.
- Every claim carries evidence: a number, a source, or a date. No "significant improvements."
- Use the active voice and present tense. "Revenue grew 18%" not "It was found that revenue had grown."
- No jargon the reader's boss wouldn't use.
- Numbers in numerals (18%, $2.4M, 3 weeks). They scan faster.
Insight extraction
A finding is not a fact; it's a fact plus its meaning. "Churn is 7%" is a fact. "Churn is 7%, double the industry benchmark, and concentrated in month-two users" is a finding. Always push to the second form.
Recommendation discipline
- Be specific enough to act on. "Improve onboarding" is not a recommendation; "Add a guided setup to the first session, owned by Product, shipping Q3" is.
- State the expected outcome and how you'll measure it.
Length guidance
- BLUF: 25-40 words.
- Each finding bullet: under 25 words.
- Whole summary: 250-350 words.
Anti-patterns
- Burying the recommendation at the bottom.
- Hedging everything ("it may possibly suggest"). Take a position; note uncertainty once.
- Restating the document's structure instead of its conclusions.
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.
- 12d ago Changed · +2 lines · +1 tokens per session f398c6c1eae8
- 1mo ago First seen · 60 lines · 153 tokens per session scan A 9d6523aaa019
executive-summary is a skill published in the GitHub repository SkillMedev/document-studio (1 stars, last pushed 12d ago), licensed MIT. It adds 154 tokens to every session and 717 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to executive-summary, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
google-apps-script
Build Google Apps Script automation for Sheets and Workspace. Custom menus, triggers (onEdit / time-driven / form submit), dialogs, sidebars, email batches, PDF export, external API. Use whenever the user wants to automate a Google Sheet, build a Sheets menu / sidebar / dialog, hit a Sheets row from email or a…
read-book
When you want to read and extract structured notes from a book — PDF, EPUB, MOBI, markdown, .txt, pasted text, or URL to a public-domain work. Reads in chunks (by chapter when a TOC exists, by 50-page blocks otherwise), extracts per-chapter TL;DR + key concepts + quotes + action items + frameworks, and offers to…
executive-summary
Redacta un resumen ejecutivo para cualquier documento, informe o propuesta. Úsalo cuando te pidan redactar un resumen ejecutivo, resumen gerencial, briefing o one-pager para stakeholders senior. Produce un resumen estructurado que directivos ocupados puedan leer en menos de 3 minutos y sobre el que puedan actuar.
invoice-generator
Create a professional, complete invoice for a client or customer. Use when asked to write an invoice, create a bill, draft a freelance/contractor invoice, or set up an invoice template. Produces a clear invoice — your and the client's details, a unique number, line items with quantities/rates, subtotal/tax/total…
dataset-datasheet
Document a dataset so others know what it is, how it was made, and when not to use it. Use when asked to write a datasheet for a dataset, document training/eval data, or assess whether a dataset is fit for a use. Produces a datasheet — motivation, composition, collection process, preprocessing, recommended uses &…
model-card
Document a deployed ML/AI model so others can use it responsibly. Use when asked to write a model card, document a model's intended use and limitations, or prepare an AI model for review/launch. Produces a complete model card — intended use, training data, evaluation metrics across slices, limitations, ethical…