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/personal-operating-modelgit 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/personal-operating-model)<a href="https://agentmods.dev/commands/pitchlab/founder-support-system/personal-operating-model"><img src="https://agentmods.dev/badge/commands/pitchlab/founder-support-system/personal-operating-model.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.00012 | $0.03420 |
| Opus 5 | $0.00006 | $0.01710 |
| Sonnet 5 | $0.00002 | $0.00684 |
| Haiku 4.5 | $0.00001 | $0.00342 |
Grade A, and why
personal-operating-model 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 — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Personal Operating Model Command
Create a comprehensive Personal Operating Model (POM) that defines how you create value, your strengths/weaknesses, failure patterns, decision system, and execution playbook.
Purpose
This command invokes the personal-operating-model skill to interactively create your operating manual covering:
- Core Loop: How you transform inputs into outputs
- Strengths: Energy-positive capabilities with evidence
- Unique Edge: Your asymmetric advantages
- Weaknesses: Structural limitations to route around
- Pitfalls: Repeating failure patterns with interrupt rules
- Decision System: How you should decide (defaults, rules, metrics)
- Operating Constraints: Your guardrails and non-negotiables
- Energy & Rhythm: Peak windows and burnout indicators
- Environment Design: Friction management and amplifiers
- Execution Playbook: Your default shipping process
- Experiments: System improvements to test
When to use: Creating your first POM, major career transitions, annual POM updates, or when patterns have shifted significantly.
Usage
/planning-strategy:personal-operating-model
No parameters needed - the skill guides you through an interactive interview.
How It Works
This command invokes the personal-operating-model skill, which:
-
Fetches context from Notion:
- Year Plan (current focus, OKRs, strategic themes)
- Golden Rules (working principles)
- Founder Wisdom (patterns to emulate)
- Previous POM (if exists)
- Optional: Recent Quarterly Logs (pattern finding)
-
Guides you through 11 sections:
- Core Loop (Input → Transformation → Output)
- Strengths (energy-positive capabilities)
- Unique Strong Points (asymmetric edge)
- Weaknesses (structural limitations)
- Pitfalls (repeating failure patterns)
- Decision System (how you decide)
- Operating Constraints (guardrails)
- Energy & Rhythm (cognitive weather map)
- Environment Design (friction management)
- Execution Playbook (how you ship)
- Experiments (system improvements)
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 · 436 lines · 12 tokens per session scan A cdac75b19f31
personal-operating-model is a command published in the GitHub repository Pitchlab/founder-support-system (2 stars, last pushed 8mo ago), licensed MIT. It adds 12 tokens to every session and 3,420 once invoked, about $0.0001 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
cancel-ralph
Cancel active Ralph Loop.
obsidian-recap
Summarize a time period from the vault - today, week, or month.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.