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/hamzafarooq/claude-code-starter/exec-summarynpx skills add hamzafarooq/claude-code-starter --skill exec-summarygit clone --depth 1 https://github.com/hamzafarooq/claude-code-starterWhat 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.00054 | $0.00334 |
| Opus 5 | $0.00027 | $0.00167 |
| Sonnet 5 | $0.00011 | $0.00067 |
| Haiku 4.5 | $0.00005 | $0.00033 |
Grade A, and why
exec-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 2d 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.
What it actually says
Ask the user to paste the document or content to summarize.
Then produce:
Executive Summary
In 30 seconds:
[1–2 sentence TL;DR — the most important thing the reader needs to know]
The 3 things that matter:
- [Most important point — frames the situation or decision]
- [Key evidence or implication — what makes this significant]
- [What's needed — a decision, approval, action, or awareness]
Decision required: [Yes / No / FYI only] If yes: [State the specific decision and the deadline]
Full summary (for a 2-minute read):
[3–4 short paragraphs. Each one advances a single point. No preamble, no "in this document we will…". Start with the most important thing.
Lead: the situation or recommendation Supporting: why, evidence, or context Risk: what could go wrong or what's uncertain Ask: what you need from the reader]
Rules:
- No passive voice
- No hedging language ("it seems like", "we believe that", "potentially")
- If the original document is vague, say so rather than fabricating precision
- Cut everything that is background the exec already knows
Ask: "Want a version formatted for a Slack message or email?"
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.
- 2d ago First seen · 43 lines · 54 tokens per session scan A 049c1bdf2f05
exec-summary is a skill published in the GitHub repository hamzafarooq/claude-code-starter (138 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 334 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…