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 saski/arnesto --skill strategic-narrativegit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/strategic-narrative)<a href="https://agentmods.dev/skills/saski/arnesto/strategic-narrative"><img src="https://agentmods.dev/badge/skills/saski/arnesto/strategic-narrative/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/saski/arnesto/strategic-narrative"><img src="https://agentmods.dev/badge/skills/saski/arnesto/strategic-narrative.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.00081 | $0.00616 |
| Opus 5 | $0.00041 | $0.00308 |
| Sonnet 5 | $0.00016 | $0.00123 |
| Haiku 4.5 | $0.00008 | $0.00062 |
Grade A, and why
strategic-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 6d 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.
This is a copy
100% identical to strategic-narrative — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
Strategic Narrative
What It Is
Strategic Narrative is a framework for crafting the one story that drives everything: sales, marketing, product, fundraising, and recruiting. The core insight: don't pitch your product as the solution to a problem — position it as the path to winning a new game the world is playing.
The traditional pitch structure is what Andy Raskin calls "the arrogant doctor": You have a problem, I have a solution, let me tell you why mine is better. This sets you up for feature comparison and bragging.
Strategic Narrative flips this entirely. Instead of leading with pain points, you lead with a shift in the world — from an old game to a new game. You're not selling a treatment; you're defining a movement and inviting people to join.
The key shift: Move from "Here's your problem, here's our solution" to "The world has changed, here's how winners are playing, and we'll help you win."
When to Use It
Use Strategic Narrative when you need to:
- Create a sales deck or pitch that resonates beyond features
- Position a product in a crowded market where feature comparison fails
- Align company teams (sales, marketing, product) around one story
- Fundraise with a compelling vision investors can rally behind
- Recruit by articulating a mission people want to join
- Differentiate from competitors without feature-by-feature comparisons
- Scale beyond founder-led sales by giving teams a story to tell
Best fit: B2B enterprise technology companies with complex products and group buying decisions.
When Not to Use It
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.
- 6d ago First seen · 59 lines · 81 tokens per session scan A 0e2eabf1a4b8
strategic-narrative is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed 3d ago), licensed Unlicense. It adds 81 tokens to every session and 616 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to strategic-narrative, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
readonly-review
Run a no-network read-only review practice with two explorer steps and one synthesis step.
repo-harness-assessment
Use when evaluating repository agent-readiness, mapping harness roles, choosing the next smallest improvement, or designing and reconciling agent entrypoints such as AGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules, or GitHub instructions.
work-state-and-delivery
Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
repo-contracts-and-boundaries
Use when turning architecture, layering, ownership, dependency direction, schemas, structural metrics, quality thresholds, baselines, allowlists, or generated quality snapshots into repository checks.
runtime-evidence-and-tracing
Use when connecting observed behavior, logs, metrics, request IDs, run IDs, screenshots, traces, external dependency results, or artifacts into a runtime evidence loop.
validation-harness-design
Use when designing repository validation commands, doctor scripts, test matrices, JSON or JUnit outputs, CI gates, smoke checks, or harness command surfaces.