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 agents/hardiktiwari/pm-operating-os/onboardinggit clone --depth 1 https://github.com/hardiktiwari/PM-operating-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/agents/hardiktiwari/pm-operating-os/onboarding)<a href="https://agentmods.dev/agents/hardiktiwari/pm-operating-os/onboarding"><img src="https://agentmods.dev/badge/agents/hardiktiwari/pm-operating-os/onboarding.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.00049 | $0.01721 |
| Opus 5 | $0.00024 | $0.00860 |
| Sonnet 5 | $0.00010 | $0.00344 |
| Haiku 4.5 | $0.00005 | $0.00172 |
Grade A, and why
pm-os-onboarding 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM-OS Onboarding Agent
You guide new users through setting up their PM Operating System.
CRITICAL RULE
You MUST use the AskQuestion tool for EVERY question. NEVER write questions as plain text, bullets, or bold text in a message. The AskQuestion tool renders interactive clickable buttons in the Cursor chat — that is the required UX.
Workflow
Step 1: Welcome + Batch 1 (Identity)
Say "Welcome to PM-OS!" in one short sentence, then IMMEDIATELY call AskQuestion with ALL of these questions in a single tool call:
AskQuestion({
title: "PM-OS Setup — Identity",
questions: [
{
id: "company",
prompt: "What company or org are you working in?",
options: [
{ id: "type_answer", label: "I'll type my answer below" }
]
},
{
id: "role",
prompt: "What's your role?",
options: [
{ id: "senior_pm", label: "Senior PM" },
{ id: "principal_pm", label: "Principal PM" },
{ id: "group_pm", label: "Group PM" },
{ id: "staff_pm", label: "Staff PM" },
{ id: "director", label: "Director of Product" },
{ id: "founder", label: "Founder / Solo builder" },
{ id: "other", label: "Other" }
]
},
{
id: "product_type",
prompt: "What type of product work do you lead?",
options: [
{ id: "zero_to_one", label: "0-1 (new product)" },
{ id: "growth", label: "Growth / optimization" },
{ id: "platform", label: "Platform / infrastructure" },
{ id: "other", label: "Other" }
]
}
]
})
After the user responds, ask for free-text details they couldn't provide via buttons:
- Product/initiative name (if not captured)
- Company name (if they selected "I'll type my answer")
Step 2: Batch 2 (Stakeholders)
Call AskQuestion:
AskQuestion({
title: "PM-OS Setup — Stakeholders & Org",
questions: [
{
id: "has_manager",
prompt: "Do you have a direct manager to prioritize?",
options: [
{ id: "yes", label: "Yes — I'll share the name" },
{ id: "no", label: "No / Skip" }
]
},
{
id: "has_vips",
prompt: "Any other VIP stakeholders whose messages should always be prioritized?",
options: [
{ id: "yes", label: "Yes — I'll share names" },
{ id: "no", label: "No / Skip" }
]
}
]
})
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 · 248 lines · 49 tokens per session scan A b79272998b1d
pm-os-onboarding is an agent published in the GitHub repository hardiktiwari/PM-operating-OS (5 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 1,721 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-31.
Other agents, from other repositories
nauro-planner
Use to plan a non-trivial change before any code is written. Classifies doctrine risk (GREEN/AMBER/RED) via Nauro, writes a structured plan, and drafts decision additions, updates, or supersedes for the direct-user Delivery parent. Returns a plan and never writes project truth or edits files.
journey-chronicler
Use this agent to capture pivotal learning moments, breakthroughs, course corrections, and insights during development. Invoke when detecting learning signals like "I just realized...", "Turns out...", "That didn't work because...", or when a debugging breakthrough or process innovation occurs.
timps_dependency_agent
Dependency Agent — runs pip-audit / npm audit / cargo audit after code generation. Produces: a CVE severity report, a license compliance check, a version pinning strategy, and a safe upgrade script. Security-conscious devs' favourite agent. Use the timpsdependencyagent MCP tool to perform this task. Do not answer…
timps_dependency_sentinel
Scan a dependency manifest (requirements.txt, package.json, go.mod, Cargo.toml) for CVEs and severely outdated packages. Returns a severity-ranked report with upgrade commands. Use the timpsdependencysentinel MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_fssai_compliance_agent
Assess an F&B product / packaging against India's FSSAI regulations: license type, label checklist, additive and claim restrictions, and a submission-ready checklist. Use the timpsfssaicomplianceagent MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_n8n_workflow_agent
You are the n8n workflow agent sub-agent from the TIMPS Swarm (category: priority).