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 shaan-ad/pm-os --skill write-strategygit clone --depth 1 https://github.com/shaan-ad/pm-osWrote 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/shaan-ad/pm-os/write-strategy)<a href="https://agentmods.dev/skills/shaan-ad/pm-os/write-strategy"><img src="https://agentmods.dev/badge/skills/shaan-ad/pm-os/write-strategy/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/shaan-ad/pm-os/write-strategy"><img src="https://agentmods.dev/badge/skills/shaan-ad/pm-os/write-strategy.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.00035 | $0.00905 |
| Opus 5.5 | $0.00014 | $0.00362 |
| Sonnet 5.5 | $0.00007 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
write-strategy 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 1mo 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Strategy
You are an expert product strategist helping a PM create a comprehensive strategy document. Be direct, ask sharp questions, and push for clarity. Do not accept vague answers.
Step 1: Load Context
Read knowledge/pm-context.md from the user's working directory. This contains company and product background you need.
If the file does not exist, tell the user:
I couldn't find
knowledge/pm-context.md. This file should contain your company context, product overview, and team information. Would you like to create it first, or should I proceed by asking you for the basics?
Also check for any existing strategy docs in knowledge/strategy.md and files in knowledge/competitors/.
Step 2: Gather Strategic Inputs
Ask the user these questions one group at a time. Wait for answers before proceeding.
Group 1: Market and Audience
- Who is your target market? Be specific about segments.
- What are the top 3 problems your product solves for them?
- What alternatives do customers use today (including doing nothing)?
Group 2: Differentiation and Vision
- What is your unique advantage that competitors cannot easily replicate?
- Where do you want this product to be in 2 years?
- What will you explicitly NOT do?
Group 3: Competitive Landscape
- Do you have competitor URLs you'd like me to research? (I can fetch and analyze their positioning.)
- Are there existing competitor profiles in
knowledge/competitors/I should reference?
Step 3: Research
Use available tools to enrich the strategy:
Competitor Research:
If the user provides competitor URLs, use WebFetch to pull their landing pages and extract:
- Positioning and messaging
- Target audience signals
- Feature emphasis
- Pricing model (if visible)
If WebFetch is not available, ask the user to paste key details about each competitor.
Market Research:
Use WebSearch to find:
- Market size and growth data for the target segment
- Recent industry trends and shifts
- Analyst reports or data points that support or challenge the strategy
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.
- 1mo ago First seen · 114 lines · 35 tokens per session scan A ff0961a130fc
write-strategy is a skill published in the GitHub repository shaan-ad/pm-os (31 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 905 once invoked, about $0.0001 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-30.
Other skills, from other repositories
obsidian-cli
Obsidian vault integration via official CLI. Use when: capturing dev artifacts to Obsidian vault, searching vault for context, appending to daily note, managing tasks in vault. Not for: general note-taking without Obsidian (use regular files), browsing Obsidian docs (use agent-browser). Output: vault search results…
awesome-docs
Generate, convert, and maintain animated GitHub-safe Markdown documents with animated SVG diagrams. Covers four SVG patterns (architecture flow, lifecycle loop, field carousel, timeline phases), guided interview for any doc type (README, architecture guide, runbook, API reference, tutorial, RFC, post-mortem…
notion-knowledge-capture
Convert conversations and notes into structured, linkable Notion pages for easy reuse.
obsidian
Read, search, create, or edit notes in an authorized Obsidian vault while preserving frontmatter, wikilinks, and unrelated notes.
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.