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 stefanoskarakasis/Product-Marketing-Skills --skill pmm-okrsgit clone --depth 1 https://github.com/stefanoskarakasis/Product-Marketing-SkillsWrote 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/stefanoskarakasis/product-marketing-skills/pmm-okrs)<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/pmm-okrs"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/pmm-okrs/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/stefanoskarakasis/product-marketing-skills/pmm-okrs"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/pmm-okrs.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.00119 | $0.03315 |
| Opus 5.5 | $0.00048 | $0.01326 |
| Sonnet 5.5 | $0.00024 | $0.00663 |
| Haiku 4.5 | $0.00012 | $0.00331 |
Grade A, and why
pmm-okrs 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 11d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pmm-okrs
A guided OKR builder for Product Marketing teams. Run it at the start of every quarter. Outputs a complete, review-ready OKR set you can paste directly into the PMM OKR Builder sheet.
Trigger
- When: Start of any quarter when setting PMM OKRs. When reviewing or stress-testing existing KRs before committing. When building a measurement plan or leadership-ready exec narrative from a finalised OKR set.
- Not for: Company-level OKR design (not PMM-specific) → general planning tool. Revenue forecasting or headcount planning. OKR tooling setup (Lattice, Workday) — this skill produces content, not configuration. If no quarterly strategy exists yet → build quarterly strategy context in your brain first, then return here.
- Example prompts:
- "Help me set our Q3 OKRs"
- "Are these KRs measurable enough?"
- "Build a scorecard for my chosen option"
- "Write OKRs for my team lead who owns competitive intelligence"
- "Stress-test this KR: improve win rate in enterprise"
- "I need to present our goals to the exec team next week"
Inputs
- Args: Company objective, PMM mandate, team size, primary metric, biggest challenge, ICP, and named competitors. All optional at start — skill gathers via intake flow.
- Defaults: If no args provided, run intake flow via
/build. If partial context is provided, infer where possible and surface gaps explicitly before proceeding. - Context keys:
/foundation/brain.md— recommended. Load Section 2 (ICP), Section 3 (Alternatives & Positioning), Section 5 (Market Context) and Section 7 (Strategy) silently if present.- Brain contract: Reads Sections 1, 2, 3, 5, 7. Writes: a Section 7 update (
quarter_goals) only as a proposal, after the user finalizes the OKR set and says yes to the exact before/after. Never writes to any other section. /context/meta-patterns.md— optional; recurring patterns the user has logged from all skills.
Pre-flight
- Gap capture (see the gap capture rule in
SKILL-SPEC.md): if a brain field this skill needs is empty or stale and the answer would change the output, ask one question: the question, one line on why it matters, "answer or skip". Answer: use it for this run and offer it as a brain update. Skip: continue with a labelled assumption and append askippedblock to/foundation/gaps.md(format inproduct-marketing-context/references/gaps-format.md). At most one gap question per run. This is the only write to/foundation/gaps.md; the skill still writes nothing else to the brain unless its own contract says so. - Personal context (see the personal context rule in
SKILL-SPEC.md): if/foundation/me.mdexists, read it for format and detail only (length, detail, shape, how blunt to be). Never take a company fact from it; the current request wins. Do not ask for it if it is missing.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago Changed · -2 lines · -11 tokens per session 253f6822420b
- 19d ago Changed · +6 lines 1470359c283e
- 1mo ago Changed · +2 lines 1bfe7128bc8a
- 2mo ago First seen · 250 lines · 130 tokens per session scan A b7cf23f47c1e
pmm-okrs is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (8 stars, last pushed 3d ago), licensed MIT. It adds 119 tokens to every session and 3,315 once invoked, about $0.0005 per session on Opus 5.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
report
A way to export a chat card or reply as a standalone HTML report, meaning a file that can open in a browser without the chat application. It preserves the card template, including right-to-left Persian or left-to-right English layouts.
k8s-rightsize
Right-size Kubernetes CPU and memory requests from Prometheus usage (p95 CPU, p98 memory over 7 days), size the node count, tune KEDA autoscaling. Use when asked to rightsize workloads, cut node cost, or "how many nodes do we need".
owasp-security
Deep OWASP reference: Top 10 2025, ASVS 5.0, secure patterns, per-language quirks, LLM Top 10 and agentic AI security. Use for an in-depth security review, auth work, or hardening an LLM or agent app. For the everyday baseline use secure-coding.
fig
One self-contained HTML file holding a looping animated SVG, for ideas that move: flows, loops, retries, queues, fan-outs. Use when the user says "fig" or a diagram would be better animated.
brand
A project-specific visual identity for chat cards and saved reports, using the project's colors, logo, and fonts. It finds these details in the repository or asks the user for them, then stores the result in a committable `.readable/` folder.
workspace-rules
A set of guidelines for deciding which rules belong in a repository's workspace instructions and which should be enforced by its build or checks.