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 cnfeat/top-pm-skills --skill setting-okrs-goalsgit clone --depth 1 https://github.com/cnfeat/top-pm-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/cnfeat/top-pm-skills/setting-okrs-goals)<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/setting-okrs-goals"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/setting-okrs-goals/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/cnfeat/top-pm-skills/setting-okrs-goals"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/setting-okrs-goals.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.00044 | $0.01056 |
| Opus 5 | $0.00022 | $0.00528 |
| Sonnet 5 | $0.00009 | $0.00211 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
setting-okrs-goals 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 9d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setting OKRs & Goals
Help the user create effective objectives and key results using frameworks and insights from 55 product leaders.
How to Help
When the user asks for help with OKRs or goal setting:
- Understand context - Ask about their company stage, team size, and whether they have existing goals or are starting fresh
- Clarify the level - Determine if these are company, department, team, or individual goals
- Identify the strategy - Ensure they have a clear strategy before setting goals (goals should be the end of strategy, not the beginning)
- Guide the structure - Help them write inspiring objectives and measurable key results that avoid common pitfalls
Core Principles
Goals should be one step from company goals
Matt LeMay: "No more than one step away from company goals. Don't let it get cascaded into oblivion." Ensure team goals orbit directly around the primary company objective rather than being buried under layers of organizational cascading.
Build systems, not just goals
Lane Shackleton: "Instead of being obsessed with the goal, be obsessed with the system that gets you there." Replace one-time OKR targets with recurring 'default-on' systems like standing customer meetings that build long-term instincts.
OKRs bridge strategy to execution
Christina Wodtke: "The main benefit is that there's a lot of concrete action through an OKR that you don't always get from strategy." Use OKRs to turn abstract strategy into concrete quarterly numbers while creating a learning cycle through end-of-quarter grading.
Triangulate with three key results
Christina Wodtke: "I like three. Something that's really hardcore numbers, something that's a little squishier like quality, and something that involves a dollar sign." Balance quantitative, qualitative, and financial metrics for a complete view of success.
Use absolute numbers, not ratios
Archie Abrams: "Ratios and percentages are dangerous metrics because they can be 'gamed' by reducing the denominator." Shift goals from 'conversion rate' to 'absolute number of users reaching a specific state' to prevent gaming.
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.
- 9d ago First seen · 78 lines · 44 tokens per session scan A ed39ed115333
setting-okrs-goals is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 1,056 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.