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 narrative-buildergit 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/narrative-builder)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/narrative-builder"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/narrative-builder/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/daddia/claude-for-strategy/narrative-builder"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/narrative-builder.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.00061 | $0.00708 |
| Opus 5.5 | $0.00024 | $0.00283 |
| Sonnet 5.5 | $0.00012 | $0.00142 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
narrative-builder 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 2mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Narrative Builder
When to use
Turn raw input into Minto pyramid: governing thought, 3–5 MECE key line points, support bullets. See ../../references/minto-pyramid.md.
What this skill does not do
- Does not produce prose memo/deck — skeleton for
deck-outline/exec-memo. - Does not paper over gaps — flags unsupported governing thoughts.
- Does not guess reader question — ask if unclear.
Preconditions
| Input | If missing |
|---|---|
| Raw findings/notes | Ask user to provide |
| Reader's real question | Ask before structuring |
| Practice profile | Default inductive; flag practice-setup |
Provisional mode
Thin input: governing thought flagged [review]; Known gaps section required.
Trust spine
- Analytical Rigor (mandatory): Outline not prose; MECE gaps/overlaps named; grouping logic stated.
- Per
trust-conventions.md.
Workflow
- Read practice profile.
- State reader's question explicitly.
- Draft governing thought (answer, not topic).
- 3–5 MECE key line points; state deductive vs inductive.
- Support sub-bullets with so-what test.
- Flag structural problems in source — don't silently fix.
Output format
GOVERNING THOUGHT: [...]
1. [Key line point 1]
- [Support]
2. [...]
Grouping logic: [deductive | inductive] — [rationale]
Known gaps / flags: [...]
Worked example
Input: Interview notes on pricing. Question: should we revert mid-tier increase?
Excerpt: Governing thought answers revert yes; three MECE key lines; gap flagged: no competitor primary research.
Quality checks before delivering
- Governing thought is the answer
- MECE explicit
- Outline format, not paragraphs
- Gaps flagged
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.
- 2mo ago First seen · 89 lines · 61 tokens per session scan A a8bd2b4c9476
narrative-builder is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 708 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-08-31.
Other skills, from other repositories
review
Run the full pre-merge panel: parallel audit and lens reviewers over a diff, consolidated into one severity-ranked verdict.
tdd
Test-driven development, from unit to end-to-end tests. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration or end-to-end tests (Playwright, Cypress). Don't use to backfill tests on existing code (/refactor) or diagnose an unknown bug (/debug).
visual-review
Two visual modes — render a PR diff as an HTML page with each hunk annotated by principle, or check a UI change in a real browser (screenshots, console, network). Use for a visual/HTML diff report, "check the UI", or "screenshot before/after". Don't use for text-only feedback (/code-review), unit tests (/tdd), or full…
to-pr
Gate, push, and open a GitHub pull request on the repo's PR template, then watch CI.
to-tickets
Slice a spec or a ticket into tracer-bullet tickets with blocking edges, published through the repo's tracker: .specs/tickets/ .md by default.
debate
Settle a go/no-go on one risky change against an alternative through an advocate, a skeptic, and a neutral investigator.