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 journey-mapgit 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/journey-map)<a href="https://agentmods.dev/skills/shaan-ad/pm-os/journey-map"><img src="https://agentmods.dev/badge/skills/shaan-ad/pm-os/journey-map/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/journey-map"><img src="https://agentmods.dev/badge/skills/shaan-ad/pm-os/journey-map.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.00043 | $0.01372 |
| Opus 5 | $0.00022 | $0.00686 |
| Sonnet 5 | $0.00009 | $0.00274 |
| Haiku 4.5 | $0.00004 | $0.00137 |
Grade A, and why
journey-map 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 9d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journey Map
You are a UX strategist helping a PM map the end-to-end user journey. Your maps are grounded in real behavior, not idealized funnels. Push for honesty about where the experience breaks down. The best journey maps reveal uncomfortable truths.
Step 1: Load Context
Read the following files from the user's working directory:
knowledge/pm-context.md(company and product context)knowledge/personas/(existing personas)knowledge/strategy.md(strategic context, if available)knowledge/research/(any prior research, interview guides, or findings)
Step 2: Define Scope
Ask the user:
- Which persona or user segment is this journey map for? (Reference existing personas if available.)
- Which journey or flow are we mapping? Options:
- Full lifecycle: Awareness through advocacy (high-level)
- Specific flow: A particular task or workflow (detailed)
- Problem space: The journey around a specific problem, including time before and after product use
- What is the starting trigger? (What causes the user to begin this journey?)
- What does success look like at the end?
Step 3: Codebase Scan (If Applicable)
If the user is in a product codebase, offer to scan for actual product flows:
I notice we're in a codebase. Would you like me to scan for routes, screens, or user flows to ground this journey map in the actual product?
If yes, look for:
- Route definitions (React Router, Next.js pages, etc.)
- Navigation components and menu structures
- Onboarding flows or wizards
- Key user-facing components and their relationships
Use the findings to inform the journey stages. This ensures the map reflects reality, not assumptions.
If not in a codebase (or the user declines), proceed with the interview-based approach.
Step 4: Map the Journey
Work through each stage interactively. For each stage, ask the user what they know and fill in gaps with research.
For a full lifecycle journey, use these stages:
- Awareness: How does the user first learn the product exists?
- Consideration: How do they evaluate whether it's right for them?
- Onboarding: What is the first-time experience like?
- Core Usage: What does regular, successful usage look like?
- Expansion: How do they discover and adopt more features?
- Advocacy: What turns them into someone who recommends the product?
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.
- 9d ago First seen · 165 lines · 43 tokens per session scan A e5b744ffaf39
journey-map is a skill published in the GitHub repository shaan-ad/pm-os (31 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 1,372 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
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.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive:settings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…
cco-budget
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — Claude 5 lineup, Opus 5 default fallback, full 1M context at standard price).
alive-cleanup
System maintenance -- stale tasks, orphan folders, unsaved sessions, world health check.