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 danielkinneyspears/federal-proposal-skills --skill writing-executive-summariesgit clone --depth 1 https://github.com/danielkinneyspears/federal-proposal-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/danielkinneyspears/federal-proposal-skills/writing-executive-summaries)<a href="https://agentmods.dev/skills/danielkinneyspears/federal-proposal-skills/writing-executive-summaries"><img src="https://agentmods.dev/badge/skills/danielkinneyspears/federal-proposal-skills/writing-executive-summaries/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/danielkinneyspears/federal-proposal-skills/writing-executive-summaries"><img src="https://agentmods.dev/badge/skills/danielkinneyspears/federal-proposal-skills/writing-executive-summaries.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.00083 | $0.01357 |
| Opus 5 | $0.00042 | $0.00678 |
| Sonnet 5 | $0.00017 | $0.00271 |
| Haiku 4.5 | $0.00008 | $0.00136 |
Grade A, and why
writing-executive-summaries 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Executive Summaries
Write the executive summary as what it actually is: the most-read, most influential pages of the proposal, and a persuasion document — not a summary. Many evaluators read the executive summary first, and it frames how they read everything after. An executive summary that recaps the table of contents wastes that position. One built around the customer's concerns and the win themes uses it.
When to use this skill
Use this skill once the win strategy exists and the volume content is at least storyboarded — the executive summary distills the win themes and previews the proposal's case, so it is written with knowledge of both. It is often drafted early for direction and finalized late once the volumes are stable.
This skill writes the executive summary specifically. General section narrative
is drafting-proposal-sections.
Inputs
Preferred upstream artifacts:
05-win-strategy.md: the win themes, discriminators, and hot buttons. The executive summary is largely the win strategy in prose.10-compliance-matrix.md: Section L rules governing the executive summary (page limit, whether it is evaluated, content restrictions).11-proposal-outline.mdand12-sections/— the proposal's actual case, so the summary previews it accurately.00-opportunity-profile.md: the customer and requirement.
Without the win strategy, the executive summary cannot be done well — it has
no themes to carry. Recommend running developing-win-strategy first.
Read ../../shared/glossary.md and ../../shared/pursuit-workspace.md if not
already read this session.
Intake
Ask these as a numbered list. Skip what upstream artifacts answer.
- Section L rules for the executive summary. Is there a page limit? Is the executive summary evaluated, or informational only? Does Section L restrict its content (for example, prohibiting information that appears only in the executive summary)?
- Customer hot buttons. What does this customer care about most? (From
05-win-strategy.mdif available.) - Win themes. What are the three to five win themes the proposal carries?
- The decision frame. In one sentence, why should this customer choose this offeror over the field?
- Format. Is the executive summary a cover letter, a standalone volume, or a section — and are graphics allowed?
What ships with it
2 files 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.
- 12d ago First seen · 125 lines · 83 tokens per session scan A 8adc8070927b
writing-executive-summaries is a skill published in the GitHub repository danielkinneyspears/federal-proposal-skills (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 83 tokens to every session and 1,357 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-31.
Other skills, from other repositories
analyzing-competitors
Produces a Black Hat competitive assessment for a US Federal opportunity as a wiki of competitor entities. Use when the user needs competitive analysis, a Black Hat review or session, competitor profiling, an incumbent assessment, or to understand the competitive field for a federal bid. Creates and enriches one…
qualifying-opportunities
Runs a structured bid/no-bid gate review for a US Federal opportunity and bootstraps the pursuit's knowledge wiki. Use when deciding whether to pursue or bid a federal solicitation, RFP, RFQ, RFI, sources-sought notice, or IDIQ task order — for a bid/no-bid decision, pursuit decision, gate review, opportunity…
igce-builder-ffp
Trigger for: FFP IGCE, firm-fixed-price estimate, FFP cost model, proposed FFP rate validation, wrap-rate analysis, Agency BPA rate comparison, price-reasonableness memo, or fair-and-reasonable analysis. Build auditable Firm-Fixed-Price federal estimates using BLS OEWS wages, layered fringe/overhead/G&A/profit, GSA…
market-research-workflow
Trigger for: federal acquisition market research; FAR Part 10 reports; refreshing an existing market research report; analyzing commerciality, competition, small-business availability, contract type, consolidation, prior awards, vendors, or market conditions; or preparing supported findings for a Pre-Award Agent. A…
acquisition-policy-workflow
Trigger for: explaining current FAR, DFARS, or agency-supplement text; determining documented acquisition-policy status for an agency and FAR part; comparing codified text, RFO model text, and agency deviations; tracing acquisition rulemaking; finding procurement comment periods; analyzing public comments; refreshing…
govcon-growth-workflow
Trigger for: finding federal opportunities; capture and bid screening; competitor or incumbent intelligence; recompete pipelines; teaming partner research; agency, customer, or market intelligence; federal labor-rate or pricing context; or refreshing prior GovCon research. Always begin with the local SAM.gov…