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 daddia/claude-for-strategy --skill performance-narrativegit 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/performance-narrative)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/performance-narrative"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/performance-narrative.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.00057 | $0.01065 |
| Opus 5 | $0.00028 | $0.00532 |
| Sonnet 5 | $0.00011 | $0.00213 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
performance-narrative 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 4d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Narrative
When to use
Turn metrics/tracker results into BLUF narrative for the audience in the practice profile — bottom line first, not metric-by-metric walkthrough.
What this skill does not do
- Does not invent actuals — flag missing numbers
[verify]. - Does not build trackers — route to
/performance:tracker-builder. - Does not replace finance sign-off — board numbers need finance validation per profile gates.
Preconditions
| Input | If missing |
|---|---|
| Metrics or tracker results | Ask user to provide |
| Practice profile (audience, cadence) | Use org default audiences; tag [PROVISIONAL] |
| Headline-worthy context | Ask what audience will act on |
Provisional mode
Without audience in profile: default to sponsor/exec; tag [PROVISIONAL]; apply quiet mode for external-facing per plugin CLAUDE.md.
Trust spine
- Confidence bands (
narrative-synthesis):- High: BLUF headline, 2–4 MECE supporting points, explicit what's-needed, sourced figures.
- Medium: Some unsourced movements tagged
[verify]. - Low: Numbers missing for headline claim — halt or narrow scope.
- Failure modes:
- Strategic advice vs. support: Narrative surfaces findings; audience decides action.
- Client confidentiality: Board/sponsor content — CONFIDENTIAL header; quiet mode for external.
- Accountability gap: What's-needed stated explicitly, not inferred.
- Analytical Rigor: MECE supporting points; so-what test on each metric.
- Incentive Gaming: N/A — narrative shape.
- Escalation triggers: Headline depends on unverified figure — tag before BLUF.
Workflow
- Read practice profile for audience and cadence.
- Identify headline — one thing audience must know this period.
- Write bottom line first — conclusion not topic.
- Group supporting metrics into 2–4 MECE points; so-what test.
- State what's needed — decision, investment, awareness.
- Full metric detail last as reference appendix.
- Connector figures. When metrics are read from
~~bi analytics,~~spreadsheet,~~crm, or other MCP sources, tag each number[sourced: <connector>, <dataset/report>, <as-of date>]per../../references/trust-conventions.md. Uncited connector figures are not allowed in board-facing output; use[verify]orINPUT NEEDEDwhen the pull fails. - MECE/falsifiability check before output.
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.
- 4d ago First seen · 109 lines · 57 tokens per session scan A 1c648d6ece70
performance-narrative is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 1,065 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-09-03.
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…
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…
codex-session
Find and inspect local Codex task conversations, including by session GUID, title, recent activity, or a phrase from the conversation. Use when the user runs /codex-session, says a prior Codex conversation died or ran out of context, wants to resume a named task, asks what a local Codex task did, or wants to continue…