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/daddia/claude-for-strategy/exec-memonpx skills add daddia/claude-for-strategy --skill exec-memogit clone --depth 1 https://github.com/daddia/claude-for-strategyWrote 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/daddia/claude-for-strategy/exec-memo)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/exec-memo"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/exec-memo.svg" alt="Measured on agentmods" 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.00049 | $0.00711 |
| Opus 5 | $0.00024 | $0.00356 |
| Sonnet 5 | $0.00010 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
exec-memo 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 5d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exec Memo
When to use
BLUF executive memo from narrative, notes, or narrative-builder output. Conclusion first per ../../references/bluf-conventions.md.
What this skill does not do
- Does not bury the bottom line — BLUF is structural, not stylistic.
- Does not exceed profile length by shrinking the bottom line — cut detail section.
- Does not ship board-final without gate — confirm + reviewer note.
Preconditions
| Input | If missing |
|---|---|
| Practice profile (length, audience) | Default one page; flag practice-setup |
| Source material or narrative | Ask for notes or run narrative-builder |
Provisional mode
Raw notes only: compress inline; label structured first pass if MECE weak.
Trust spine
Per trust-conventions.md — sourcing, assumptions, numbers, confidence, gate before exec-final.
- Analytical Rigor: Every WHY point traces to support; cut non-load-bearing detail.
- Escalation: Ask missing → make impossible to miss; unverified claims → tag not smooth over.
Workflow
- Read practice profile.
- Use
narrative-builderoutput if available; else compress notes inline. - Bottom line first (1–2 sentences, the answer).
- WHY: 2–4 MECE points.
- ASK: decision/resource/sign-off if any.
- DETAIL: optional background last.
- Check length vs profile.
Output format
[BOTTOM LINE]
WHY:
1. [point]
2. [point]
ASK: [or omit]
DETAIL: [...]
Worked example
Input: Notes on pricing failure. Bottom line: revert mid-tier increase.
Excerpt: BLUF states revert; WHY three MECE points (volume, elasticity, competitor); ASK: CFO sign-off by Friday.
Quality checks before delivering
- Bottom line before context
- MECE WHY section
- ASK visible if needed
- Length vs profile
- Trust spine on figures
Propose profile update
When a stable convention surfaces during this run (thresholds, naming, tone, output format, or recurring corrections), propose a profile update: show the exact diff against ~/.claude/plugins/config/claude-for-strategy/consulting/CLAUDE.md (org-wide facts go to org-profile.md), ask for confirmation, and write only on yes. Only /consulting:practice-setup auto-applies a full profile write.
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.
- 5d ago First seen · 92 lines · 49 tokens per session scan A e5d59310c7e3
exec-memo is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 711 once invoked, about $0.0002 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
swarmclaw
AI agent runtime and multi-agent orchestration platform. Teaches agents how to use SwarmClaw's 6 primitive tools, persistent memory, dreaming, delegation, connectors, credentials, and the skill system. Use when an agent is running on SwarmClaw and needs to understand the platform's capabilities.
spec-herdr-review
Run visible multi-agent spec reviews in Herdr through interactive agent CLIs such as Claude, Codex, Copilot/GLM, or Grok/Composer. Supports two modes — a spec review (the design, before implementation) and an implementation review (the implemented diff vs the spec, after the calling model has built it). Ask for…
spec
Spec-driven development in the active repository's spec/{feature}/ directory. Use when user says /spec, "write a spec", "plan a feature", "create a PRD", "spec status", "spec out this epic", or references spec/ directory. Sizes work from small to epic, where an epic is a parent spec with numbered child specs.…
gpmc
Read-only Active Directory Group Policy inventory via LDAP — list GPOs, show OU/site links (enabled/disabled/enforced), find unlinked GPOs, search by name, and gpresult for the current user. Use when the user asks about GPOs, Group Policy, GPMC, linked vs unlinked policies, RSoP, what applies to this user, or runs…
grok-session
Find and inspect local Grok CLI conversations by session GUID, title, phrase, or recent activity. Use when the user runs /grok-session, asks what Grok work they have been doing lately, says a Grok conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named session, or wants to continue…
claude-session
Find and inspect local Claude Code conversations by session GUID, title, phrase, or recent activity. Use when the user runs /claude-session, asks what Claude Code work they have been doing lately, says a Claude Code conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named…