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/sananthanarayan/skilldrop/exec-summarynpx skills add sananthanarayan/skilldrop --skill exec-summarygit clone --depth 1 https://github.com/sananthanarayan/skilldropWhat 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.00067 | $0.00774 |
| Opus 5 | $0.00034 | $0.00387 |
| Sonnet 5 | $0.00013 | $0.00155 |
| Haiku 4.5 | $0.00007 | $0.00077 |
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 yesterday.
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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
exec-summary
You help the user turn dense technical material into a one-page brief that a VP can read between meetings and act on.
How to respond
-
Get the source. Either the user pastes the full doc, gives you a file path, or describes the project verbally. If the source is more than ~3000 words, ask them to confirm scope: "Is this for [audience X] who already knows [Y]?"
-
Identify the audience. A one-pager for an exec sponsor is different from one for finance is different from one for a partner. Default audience is "senior leader who is not an engineer, has 60 seconds, and needs to approve or push back."
-
Use
templates/exec-summary.md— six fixed sections:- The Ask (one line — what decision/approval are we requesting?)
- TL;DR (three bullets — what's the project, why now, what's the recommendation)
- Business impact (revenue / cost / risk / time — quantified where possible)
- Cost & timeline (rough numbers — say "rough" if they are)
- Risks & how we're managing them (max 3 — pick the ones the exec would ask about)
- What we need from you (concrete asks — money, headcount, an exec decision, a connection)
-
Compress ruthlessly. A one-pager is one page — about 300–400 words rendered, including the headers. Cut:
- Adjectives ("robust", "scalable", "next-generation")
- Hedging ("we believe", "in many cases")
- Technical jargon (replace or define inline once)
- History the audience already knows
-
Lead with the conclusion. Execs read top-to-bottom and stop when they have what they need. The Ask + TL;DR must be self-contained — if those are all the exec reads, they should be able to make a decision.
Quality bar
- Quantify or qualify. Numbers are best ("$2.4M ARR at risk"), but if you don't have numbers, say "directional" rather than inventing precision.
- Plain language. A non-engineer should not encounter a term they don't recognize in the first paragraph.
- No internal-team-speak. "OKRs", "swimlanes", "north-star metric" are okay; "sharding strategy", "eventually consistent", "blue-green" need translation or replacement.
- Active voice, second person where natural. "You'll need to approve the budget" beats "budget approval will be required".
What ships with it
4 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.
- yesterday First seen · 46 lines · 67 tokens per session scan A 943adf202f94
exec-summary is a skill published in the GitHub repository sananthanarayan/skilldrop (2 stars, last pushed 18d ago), licensed MIT. It adds 67 tokens to every session and 774 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-31.
Other skills, from other repositories
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
openlore-execute-refactor
Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.
openlore-plan-refactor
Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.
openlore-debug
Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.
openlore-analyze-codebase
Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.
team-repair
Re-index OKF v0.2 index.md/log.md files, derive CDR.md, rebuild .skills.json and AGENTS.md in team-ai-directives, migrate v0.1→v0.2 frontmatter, scan for rule conflicts, and verify directive freshness. Use when indexes are inconsistent, orphans are detected, after bulk changes, or for periodic team AI directives…