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 strategy-connectorgit 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/strategy-connector)<a href="https://agentmods.dev/skills/hardiktiwari/pm-operating-os/strategy-connector"><img src="https://agentmods.dev/badge/skills/hardiktiwari/pm-operating-os/strategy-connector/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/strategy-connector"><img src="https://agentmods.dev/badge/skills/hardiktiwari/pm-operating-os/strategy-connector.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.00037 | $0.00528 |
| Opus 5 | $0.00018 | $0.00264 |
| Sonnet 5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
strategy-connector 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 12d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategy Connector
Help PMs map work items to strategic goals and OKRs. Ensures features, experiments, and initiatives are explicitly tied to organizational strategy and measurable outcomes.
When to Use
- Before writing a PRD
- Backlog prioritization
- Quarterly or annual planning
- Leadership presentations
- When asked "how does this tie to strategy?"
- Justifying resource allocation
Process / Template
1. Understand the Work Item
- What is it? (feature, experiment, initiative)
- Who is it for?
- What problem does it solve?
- What's the expected outcome?
2. Reference Strategic Context
- Pull from
knowledge/_template/strategy.md(or your org's strategy doc) - Identify: strategic pillars, OKRs, key metrics, target segments
- Note: what is the organization optimizing for?
3. Map the Connection
For the work item, articulate:
Strategic Pillar
- Which pillar or theme does this support?
- How does it advance that pillar?
OKR / Goal
- Which objective or key result does this contribute to?
- What's the causal path? (this work → metric movement → OKR)
Segment / Persona
- Which customer segment or persona does this serve?
- Is this segment a strategic priority?
Metric Impact
- What metric(s) will this move?
- Direction and rough magnitude (if known)
4. Validate the Link
- Is the connection explicit and defensible?
- Could someone challenge it? How would you respond?
- Are there stronger or weaker links to call out?
5. Document the Mapping
Strategy Mapping
| Work Item | Strategic Pillar | OKR/Goal | Segment | Metric Impact |
|---|---|---|---|---|
| [Feature/Experiment] | [Pillar] | [OKR] | [Segment] | [Metric + direction] |
Narrative
- 2–3 sentences: how this work advances strategy
Output
A Strategy Mapping that:
- Explicitly connects the work item to strategy
- Identifies the OKR or goal it supports
- Clarifies segment and metric impact
- Provides a defensible narrative for prioritization and planning
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.
- 12d ago First seen · 79 lines · 37 tokens per session scan A 4a6b07f67a3b
strategy-connector is a skill published in the GitHub repository hardiktiwari/PM-operating-OS (5 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 528 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
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.
handoff
Guides the Claude Code agent through completing a task, selecting a handoff tier, building a valid completion-card, and performing a clean task handoff.
execute-plan
Implement a written plan (from write-plan or interview-plan) when the user says execute or implement it. Loads the plan, executes ready tasks in waves in the ticket venue, runs the plan's review gate itself. Do not use while still interviewing or writing the plan.
generate-stories
Translate a single Epic into clear, actionable User Stories with explicit acceptance criteria. Activate when an Epic is defined and work needs to be prepared for Delivery execution.
review-input
Adversarial review of any input (human idea, agent analysis, research report, feedback, observation) BEFORE it mutates persistent project state. Universal interceptor with domain auto-detection, 2-phase classification + evaluation, and triple-verdict output (veracity / fit / actionability). Anti-girouette guardrail…
review-story-alignment
Adversarial review of generated stories against the Discovery Session Brief, referenced DECs, and Epic DoR. Detects contradictions, omissions, and intent drift BEFORE stories reach Delivery. Produces a structured verdict (PASS/FAIL) with specific findings per story. Triggers after generate-stories, before backlog…