executive-briefing

executive-briefing is a skill for Codex from jeremylongworth-source/AgentSkills. It costs 58 tokens per session (352 once invoked), scanned A, original, MIT.

A short briefing that turns business updates, metrics, risks, and open decisions into information for company leaders.

In plain words
What is it for?
Use it for weekly CEO updates, operating reviews, strategic snapshots, and one-page leadership summaries.
Why use it?
It helps leaders quickly see what changed, what matters, and where their attention or decisions are needed.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex.

Good fit Use it for weekly CEO updates, operating reviews, strategic snapshots, and one-page leadership summaries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeremylongworth-source/agentskills/executive-briefing
Install

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.

Any agent
npx skills add jeremylongworth-source/AgentSkills --skill executive-briefing
Clone the repo
git clone --depth 1 https://github.com/jeremylongworth-source/AgentSkills

Made for: Codex.

Wrote 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.

agentmods badge for executive-briefing

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/executive-briefing/github.svg)](https://agentmods.dev/skills/jeremylongworth-source/agentskills/executive-briefing)
Your own site
<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/executive-briefing"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/executive-briefing/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.

agentmods 80×15 button for executive-briefing

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/executive-briefing"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/executive-briefing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 352 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.00352
Opus 5.5 $0.00023 $0.00141
Sonnet 5.5 $0.00012 $0.00070
Haiku 4.5 $0.00006 $0.00035

Measured 1mo ago against content hash 20db29b54412, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

executive-briefing 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 1mo 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.

skills/executive-briefing/SKILL.md · 47 lines

What it actually says

Executive Briefing

Core Workflow

  1. Identify the audience, decision horizon, period, business context, and intended use of the brief.
  2. Gather supplied signals: metrics, customer issues, revenue, product, delivery, finance, hiring, risks, decisions, and open actions.
  3. Separate facts, assumptions, risks, decisions needed, and recommended focus.
  4. Prioritize what changed, what matters, what needs attention, and what can wait.
  5. Keep the brief short enough for an executive to review quickly.
  6. End with decisions requested, owner follow-ups, and unresolved questions.

Safety Rules

  • Do not invent metrics, commitments, customer facts, board facts, or financial figures.
  • Do not turn weak signals into confident strategic conclusions.
  • Flag missing data, stale context, and unverified claims.
  • Require review before external, board, investor, customer, legal, or finance use.

Deliverable Shape

For executive briefings, provide:

  • Context and time period
  • Top changes since last review
  • Priority issues and opportunities
  • Key metrics or signals
  • Decisions needed
  • Risks and mitigations
  • Owner actions
  • Open questions

References

  • Read references/executive-briefing-checklist.md when preparing a CEO, founder, owner, leadership, or weekly executive brief.
Files

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.

Changes

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.

  1. 1mo ago First seen · 47 lines · 58 tokens per session scan A 20db29b54412

Subscribe to this mod's changes

executive-briefing is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 58 tokens to every session and 352 once invoked, about $0.0002 per session on Opus 5.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-09-03.

Related

Other skills, from other repositories

issue-authoring

Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…

kurone-kito/idd-skill · 71 tokens

analiz-task-spec

Use when opening an analiz task for the system-architect - the required fields, what the criteria may say, and what the description must hand over.

makifbaysal/tasktrooper · 34 tokens

answer-workspace-questions

Use when the stakeholder asks a factual or status question about the workspace - call the matching read tool and answer conversationally, without creating tasks or asking for approval.

makifbaysal/tasktrooper · 37 tokens

call-prep

Create or review call prep deliverables with traceable assumptions, decision criteria, ownership, and risk controls. Use when the user asks for call prep planning or analysis.

sandbaseai/sandbase-skills · 37 tokens

wicked-garden-product

Product domain skill: 13 user-invokable actions — a11y | acceptance | align | analyze | elicit | listen | mockup | screenshot | strategy | synthesize | ux | ux-review | visual-direction — backed by the rubrics in refs/ and this domain's knowledge-module sub-skills. Use when: "accessibility audit", "WCAG compliance"…

mikeparcewski/wicked-garden · 190 tokens

wicked-garden-swarm

Parallel verification-swarm orchestration playbook: fan out N scoped subagents over N units of work (repos / modules / files), then run a SEPARATE verifier wave that re-derives each result from a clean state — self-graded "done" is rejected. Composes the crew agents, the qe semantic-reviewer, /wicked-garden:prove…

mikeparcewski/wicked-garden · 198 tokens