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 agentmods add commands/pitchlab/founder-support-system/year-plangit clone --depth 1 https://github.com/Pitchlab/founder-support-systemWrote 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/commands/pitchlab/founder-support-system/year-plan)<a href="https://agentmods.dev/commands/pitchlab/founder-support-system/year-plan"><img src="https://agentmods.dev/badge/commands/pitchlab/founder-support-system/year-plan.svg" alt="Measured on agentmods" 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.00009 | $0.01645 |
| Opus 5 | $0.00005 | $0.00822 |
| Sonnet 5 | $0.00002 | $0.00329 |
| Haiku 4.5 | $0.00001 | $0.00164 |
Grade A, and why
year-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 5d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Year Plan Command
Create or update your comprehensive Year Plan with focused OKRs, financial targets, quarterly themes, and strategic constraints.
Rule: If it doesn't move one of your OKR bars, it's a distraction.
Purpose
This command guides you through an interactive annual planning session that:
- Defines your strategic theme and one-year outcome
- Sets concrete financial targets and kill criteria
- Establishes 2-3 focused OKRs (Financial, Visibility, Development)
- Plans quarterly focus areas and priorities
- Defines positioning, visibility, and network goals
- Identifies risks and anti-goals
- Produces an updated Year Plan page in Notion
Usage
/planning-strategy:year-plan
No arguments required - The skill will guide you interactively.
How It Works
This command invokes the year-plan skill, which:
- Determines the current year using
/general:get-year-and-quarter - Fetches reference materials from Notion:
- Vision (manifesto)
- Personal Operating Model
- Golden Rules
- Current Year Plan (if exists)
- Recent Quarterly Logs
- Guides you interactively through 11 sections:
- Strategic Theme & North Star
- Financial Plan (revenue, profit, safety)
- Objectives & Key Results (2-3 OKRs)
- Quarterly Focus (themes and priorities)
- Operating Priorities (weekly habits, time allocation)
- Visibility & Positioning
- Network & Leverage
- Product/IP Bets (optional)
- Risks & Anti-Goals
- Review Cadence
- Strategic Dashboard (progress tracking)
- Checks Vision alignment to ensure coherence
- Updates Notion Year Plan page after confirmation
- Archives old plan at the end of the document
What You'll Need
Time: 60-90 minutes of focused strategic thinking
Information:
- Last year's performance (if available)
- Financial targets and constraints
- Strategic priorities and focus areas
- Key capabilities to develop
- Market positioning ideas
Output
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.
- 5d ago First seen · 240 lines · 9 tokens per session scan A fe5631bd3e07
year-plan is a command published in the GitHub repository Pitchlab/founder-support-system (2 stars, last pushed 8mo ago), licensed MIT. It adds 9 tokens to every session and 1,645 once invoked, about $0.0000 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.