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 jezweb/claude-skills --skill strategy-documentgit clone --depth 1 https://github.com/jezweb/claude-skillsWrote 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/jezweb/claude-skills/strategy-document)<a href="https://agentmods.dev/skills/jezweb/claude-skills/strategy-document"><img src="https://agentmods.dev/badge/skills/jezweb/claude-skills/strategy-document.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector pass
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.00079 | $0.02715 |
| Opus 5 | $0.00039 | $0.01358 |
| Sonnet 5 | $0.00016 | $0.00543 |
| Haiku 4.5 | $0.00008 | $0.00271 |
Grade A, and why
strategy-document 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategy Document Writer
Produces strategic documents that are specific enough to act on. The quality bar: every statement should be falsifiable ("We have 3 React developers with 10+ years experience" vs "We have a strong team") and every recommendation should be implementable within a defined timeframe.
Process
Step 1: Determine the mode
Ask the user which document type they need:
- SWOT analysis — assess current position
- Business plan (lean or full) — articulate the business model
- OKRs / Goals — set measurable objectives
- Competitive analysis — understand the market landscape
If the user is unsure, ask what decision they are trying to make. That usually reveals the right mode:
- "Should we enter this market?" -> Competitive analysis + SWOT
- "What should we focus on this quarter?" -> OKRs
- "We need funding / a partner deck" -> Business plan
- "Something feels off but I can't pinpoint it" -> SWOT
Step 2: Gather context
Ask for:
- Business name, industry, size (team, revenue if comfortable sharing)
- Current situation (what prompted this exercise?)
- Key competitors (if known)
- Time horizon (this quarter, this year, 3-year)
- Audience for the document (internal team, board, investors, bank, personal clarity)
The audience determines the level of detail. A bank wants financial projections. A founder wants clarity. A team wants direction.
Step 3: Draft and validate
Write the document, then review every entry against the specificity test: could this statement apply to any business in the industry? If yes, it is too vague. Rewrite with the user's specific context.
Mode 1: SWOT Analysis
Structure
Present as a 2x2 grid with 3-5 points per quadrant. Each point is one sentence — specific and actionable.
HELPFUL HARMFUL
to achieving objectives to achieving objectives
INTERNAL STRENGTHS WEAKNESSES
(origin) - ... - ...
- ... - ...
EXTERNAL OPPORTUNITIES THREATS
(origin) - ... - ...
- ... - ...
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 · 250 lines · 79 tokens per session scan A a958b28a2533
strategy-document is a skill published in the GitHub repository jezweb/claude-skills (995 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 2,715 once invoked, about $0.0004 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
code-transfer
Transfer code between files with line-based precision. Use when users request copying code from one location to another, moving functions or classes between files, extracting code blocks, or inserting code at specific line numbers.
ensemble-solving
Generate multiple diverse solutions in parallel and select the best. Use for architecture decisions, code generation with multiple valid approaches, or creative tasks where exploring alternatives improves quality.
conversation-analyzer
Analyzes your Claude Code conversation history to identify patterns, common mistakes, and opportunities for workflow improvement. Use when user wants to understand usage patterns, optimize workflow, identify automation opportunities, or check if they're following best practices.
code-execution
Execute Python code locally with marketplace API access for 90%+ token savings on bulk operations. Activates when user requests bulk operations (10+ files), complex multi-step workflows, iterative processing, or mentions efficiency/performance.
code-refactor
Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated code patterns, updating method calls, or making consistent changes across multiple locations.
feature-planning
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.