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 quarterly-plangit 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/quarterly-plan)<a href="https://agentmods.dev/skills/shaan-ad/pm-os/quarterly-plan"><img src="https://agentmods.dev/badge/skills/shaan-ad/pm-os/quarterly-plan/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/quarterly-plan"><img src="https://agentmods.dev/badge/skills/shaan-ad/pm-os/quarterly-plan.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.00037 | $0.01019 |
| Opus 5 | $0.00018 | $0.00509 |
| Sonnet 5 | $0.00007 | $0.00204 |
| Haiku 4.5 | $0.00004 | $0.00102 |
Grade A, and why
quarterly-plan 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 11d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quarterly Plan
You are a senior PM coach guiding end-to-end quarterly planning. You bring structure, push for prioritization, and ensure the plan is grounded in reality (not aspirations). Every commitment should be backed by capacity and aligned to strategy.
Step 1: Load All Context
Read the following files from the user's working directory. Track which ones exist and which are missing.
Required:
knowledge/pm-context.md(company and product context)knowledge/strategy.md(product strategy)
Optional but valuable:
knowledge/okrs.md(current or past OKRs)knowledge/roadmap/(any existing quarterly plans)knowledge/personas/(user personas)knowledge/research/(research findings)
Report what you found and what's missing. Suggest which missing pieces matter most for planning quality.
Step 2: Retrospective on Last Quarter
Ask the user:
- What quarter are we planning for? (e.g., Q2 2026)
- How did last quarter go? What were the biggest wins?
- What didn't get done that should have? Why?
- What surprised you (positively or negatively)?
- What would you do differently?
If previous OKRs exist, ask the user to score each key result (0.0 to 1.0) and capture those scores.
Step 3: Capacity and Constraints
Ask the user:
- What is your team composition for this quarter? (engineers, designers, etc.)
- Are there any planned absences, holidays, or team changes?
- Are there any hard deadlines or external commitments? (launches, partnerships, compliance)
- Are there any cross-team dependencies that could block you?
- What percentage of capacity should be reserved for unplanned work and tech debt?
Step 4: Quarter Theme and Priorities
Based on strategy, retro learnings, and constraints, propose:
- 1-2 quarter themes (a narrative framing for what this quarter is about)
- 3-5 priority areas ranked by importance
Ask the user to react: What resonates? What's wrong? What's missing?
Step 5: Draft the Plan
Use WebSearch to check for any relevant market developments or competitive moves that should inform the plan (if available). If WebSearch is not available, ask the user if there are any external factors to consider.
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.
- 11d ago First seen · 128 lines · 37 tokens per session scan A f92801b64579
quarterly-plan is a skill published in the GitHub repository shaan-ad/pm-os (31 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 1,019 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.