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 gtmagents/gtm-agents --skill exec-briefinggit clone --depth 1 https://github.com/gtmagents/gtm-agentsWrote 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/gtmagents/gtm-agents/exec-briefing)<a href="https://agentmods.dev/skills/gtmagents/gtm-agents/exec-briefing"><img src="https://agentmods.dev/badge/skills/gtmagents/gtm-agents/exec-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.
<a href="https://agentmods.dev/skills/gtmagents/gtm-agents/exec-briefing"><img src="https://agentmods.dev/badge/skills/gtmagents/gtm-agents/exec-briefing.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.00026 | $0.00300 |
| Opus 5.5 | $0.00010 | $0.00120 |
| Sonnet 5.5 | $0.00005 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
exec-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.
What it actually says
Executive Briefing Kit Skill
When to Use
- Preparing QBR/EBR agendas that include executive stakeholders.
- Summarizing account impact stories for CRO/CEO/CTO readouts.
- Documenting commitments and follow-ups after executive meetings.
Framework
- Audience Lens – capture what each executive cares about (business outcomes, risk, roadmap, financial impact).
- Narrative Structure – headline, metrics, proof, decisions/asks, next steps.
- Visual Layer – standardized slides/one-pagers with consistent KPIs and color coding.
- Decision Log – track approvals, risks, and owners for follow-ups.
- Distribution Plan – define recipients, timing, and archival location.
Templates
- Briefing Doc: See
templates/briefing_doc.mdfor agenda and summary structure. - Executive summary slide (headline, impact, next action).
- Meeting brief (objectives, attendees, agenda, prep requirements).
- Decision log table with owners and deadlines.
Tips
- Keep top section under 150 words; move detail to appendix.
- Pair with
success-planning-frameworkto ensure talking points align to milestones. - Send recap within 24 hours to reinforce commitments.
What ships with it
1 file 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.
- 1mo ago First seen · 33 lines · 26 tokens per session scan A 354696942d1d
exec-briefing is a skill published in the GitHub repository gtmagents/gtm-agents (428 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 300 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…