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 hardiktiwari/PM-operating-OS --skill one-pagergit 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/skills/hardiktiwari/pm-operating-os/one-pager)<a href="https://agentmods.dev/skills/hardiktiwari/pm-operating-os/one-pager"><img src="https://agentmods.dev/badge/skills/hardiktiwari/pm-operating-os/one-pager/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/hardiktiwari/pm-operating-os/one-pager"><img src="https://agentmods.dev/badge/skills/hardiktiwari/pm-operating-os/one-pager.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.00036 | $0.00458 |
| Opus 5 | $0.00018 | $0.00229 |
| Sonnet 5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
one-pager 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 10d 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.
What it actually says
One-Pager
Help PMs write feature one-pagers: lightweight alignment documents that capture the essentials without the full structure of a PRD. Ideal for quick buy-in and shared understanding.
When to Use
- Aligning stakeholders before a full PRD
- Pitching a new feature or initiative
- Quick spec for a small scope
- When a full PRD is overkill
- Exploratory or early-stage ideas
Process / Template
1. Gather Core Information
- What is the feature or initiative?
- Who is it for? (persona/segment)
- What problem does it solve?
- What does success look like? (metric or outcome)
- What's the proposed approach?
2. Use the One-Pager Structure
Title & One-Liner
- Feature name and 1-sentence description
Problem
- Customer problem (1–2 sentences)
- Optional: business problem or opportunity
Proposed Solution
- What we're building (3–5 bullets)
- Key flows or changes
- Out of scope (what we're not doing)
Success Metrics
- Primary metric and target
- How we'll measure
Risks & Assumptions
- Key assumptions we're making
- Risks or unknowns
Timeline
- High-level milestones (optional)
- Target launch or phase
Open Questions
- Decisions needed
- Dependencies to resolve
3. Keep It Tight
- Aim for 1 page (or equivalent in markdown)
- Bullets over paragraphs
- No more than 5–7 sections
- Skip implementation detail
4. Validate Alignment
- Does it answer: What? Why? Who? How we'll know?
- Can a stakeholder understand it in 2 minutes?
- Are open questions explicit?
Output
A One-Pager document that:
- Fits on one page or screen
- Enables quick alignment
- Can be expanded into a PRD later
- Serves as a shared reference for the team
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.
- 10d ago First seen · 78 lines · 36 tokens per session scan A c3a29c2e5177
one-pager is a skill published in the GitHub repository hardiktiwari/PM-operating-OS (5 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 458 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 skills, from other repositories
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
firebase-cloud-functions
Use when calling callable functions (httpsCallable), passing data to server-side logic, handling function errors/timeouts, configuring regions, or testing with the Emulator Suite.
excalidraw-architect
Choose and compose the right Excalidraw diagram - architecture, flowchart, sequence, state, ER, swimlane, process, timeline, quadrant, pyramid, venn, loop, gantt, bar, line, scatter, and more - using the excalidraw-architect-mcp server. Use whenever a reader would learn more from a picture than from prose, or when…
sdd
Execute the Liatrio Spec-Driven Development (SDD) workflow when explicitly invoked by the user. NOTE: this skill is NOT intended to be dynamically loaded or automatically triggered; it should only ever be explicitly called by the user.
bcc-throughline
BCC global progress cockpit (plans.md/progress.md/findings.md). Slash: /bcc-throughline · chat: bcc:throughline · "where are we" · reprioritize · resume after /clear. Not for coding or full PLAN grill.