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 skills/hardiktiwari/pm-operating-os/exec-communicatornpx skills add hardiktiwari/PM-operating-OS --skill exec-communicatorgit 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/exec-communicator)<a href="https://agentmods.dev/skills/hardiktiwari/pm-operating-os/exec-communicator"><img src="https://agentmods.dev/badge/skills/hardiktiwari/pm-operating-os/exec-communicator.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 | $0.00034 | $0.00595 |
| Opus 5 | $0.00017 | $0.00298 |
| Sonnet 5 | $0.00007 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
exec-communicator 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 4d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Exec Communicator
Help PMs write clear, executive-ready communications using BLUF (Bottom Line Up Front) format. Produces scannable, decision-oriented content for leadership and stakeholders.
When to Use
- Writing weekly or bi-weekly status updates
- Escalating a risk or blocker to leadership
- Requesting a decision from stakeholders
- Drafting internal launch announcements for executives
- Preparing quarterly business review input
- When asked "help me write this for leadership"
Process / Template
1. Identify Communication Type
Ask: What type of communication is needed?
- Status update — progress vs. plan, metrics, risks
- Escalation — issue, impact, options, recommendation
- Decision request — context, options, trade-offs, deadline
- Launch announcement — what shipped, who it's for, impact
2. Gather Key Inputs
- What happened? (facts, metrics, outcomes)
- What's at risk? (blockers, dependencies)
- What do you need? (decision, resources, air cover)
- When is the deadline?
3. Apply BLUF Principles
- Lead with the "so what" — one sentence summary first
- Be specific — numbers, dates, named stakeholders
- Tie to metrics and strategy — connect to goals and OKRs
- Anticipate questions — address likely objections proactively
- Keep it scannable — bullets over paragraphs, headers for sections
4. Use the Right Template
Status Update:
- TL;DR — one sentence summary
- Progress vs. Plan — on track / at risk / behind
- Key Metrics — numbers that matter
- Risks/Blockers — what could derail
- Asks — what you need from leadership
Escalation:
- Issue — what's wrong (1–2 sentences)
- Impact — quantified (revenue, timeline, customers)
- Options — 2–3 paths forward with pros/cons
- Recommendation — what you recommend and why
- Timeline — when a decision is needed
Decision Request:
- Context — 2 sentences max
- Decision Needed — explicit ask
- Options with Trade-offs — pros/cons per option
- Recommendation — your call
- Deadline — when to decide
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.
- 4d ago First seen · 70 lines · 34 tokens per session scan A a60278e99042
exec-communicator is a skill published in the GitHub repository hardiktiwari/PM-operating-OS (5 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 595 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
kayba-stage-5-action-plan
Triage each insight into discard/code-fix/prompt-fix and produce a prioritized action plan with specific recommendations. Trigger when the user says "run stage 5", "make action plan", "triage skills", or when invoked by the kayba-pipeline orchestrator. Requires eval outputs from stages 1-4.
kayba-stage-2-domain-context
Gather domain context about the repository and agent — system prompt, tool definitions, domain docs, and behavior patterns from traces. Trigger when the user says "run stage 2", "gather context", "domain context", or when invoked by the kayba-pipeline orchestrator.
kayba-stage-7-fixer
Implement the approved fixes from the action plan and log all changes. Trigger when the user says "run stage 7", "implement fixes", "apply action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md to exist.
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.