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 wdavidturner/product-skills --skill okrsgit clone --depth 1 https://github.com/wdavidturner/product-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/wdavidturner/product-skills/okrs)<a href="https://agentmods.dev/skills/wdavidturner/product-skills/okrs"><img src="https://agentmods.dev/badge/skills/wdavidturner/product-skills/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/wdavidturner/product-skills/okrs"><img src="https://agentmods.dev/badge/skills/wdavidturner/product-skills/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.00105 | $0.01094 |
| Opus 5 | $0.00053 | $0.00547 |
| Sonnet 5 | $0.00021 | $0.00219 |
| Haiku 4.5 | $0.00011 | $0.00109 |
Grade A, and why
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OKRs (Objectives and Key Results)
What It Is
OKRs are a goal-setting framework that creates focus, alignment, and a learning cycle for teams and organizations. The core insight: set one ambitious objective per quarter with 2-3 measurable key results, then check in weekly to maintain focus.
The key shift: Move from tracking activities ("What are we doing?") to tracking outcomes ("What progress are we making toward our goals?").
OKRs are a vitamin, not a medicine. They supercharge companies that already have their fundamentals in place (strategy, empowered teams, psychological safety). They won't fix broken organizations - they'll just reveal what's broken.
Credit: Originated by Andy Grove at Intel. Popularized by John Doerr who brought it to Google. Christina Wodtke's Radical Focus provides the most practical implementation guidance.
When to Use It
Use OKRs when you need to:
- Focus the team on the single most important thing for the quarter
- Align the organization so everyone knows what matters most
- Create accountability with measurable outcomes (not just activities)
- Build a learning cycle through weekly check-ins and quarterly retrospectives
- Scale leadership so founders/executives don't need to micromanage
- Accelerate progress by avoiding the "peanut butter" problem of spreading effort too thin
When Not to Use It
- You don't have a clear strategy (OKRs reveal missing strategy, they don't replace it)
- Your company lacks psychological safety (people will sandbag or game the metrics)
- You want to track ALL the work (OKRs are for priorities, not comprehensive task lists)
- Teams aren't empowered to decide HOW to achieve outcomes
Patterns
Detailed examples showing how to apply OKRs correctly. Each pattern shows a common mistake and the correct approach.
Critical (get these wrong and you've wasted your time)
| Pattern | What It Teaches |
|---|---|
| key-results-are-tasks | Key results must be outcomes, not activities or deliverables |
| too-many-okrs | One objective per quarter — not five, not ten |
| missing-strategy | OKRs without strategy is just goal theater |
| boring-objectives | Objectives should make you want to get out of bed |
| no-weekly-checkins | Set and forget kills OKRs — the cadence is the system |
What ships with it
16 files 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.
- patterns/_template.md 460 B
- patterns/annual-okrs.md 1.6 KB
- patterns/boring-objectives.md 1.5 KB
- patterns/cascading-trap.md 1.9 KB
- patterns/fluffy-objectives.md 1.5 KB
- patterns/grading-without-learning.md 1.6 KB
- patterns/key-results-are-tasks.md 1.5 KB
- patterns/missing-strategy.md 1.7 KB
- patterns/no-weekly-checkins.md 1.5 KB
- patterns/okrs-for-everything.md 1.7 KB
- patterns/perfect-measurement.md 1.5 KB
- patterns/sandbagging-goals.md 1.5 KB
- patterns/skipping-celebrations.md 1.4 KB
- patterns/slow-approval-process.md 1.5 KB
- patterns/too-many-okrs.md 1.5 KB
- references/okrs-playbook.md 13 KB
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 First seen · 89 lines · 105 tokens per session scan A 3798b02093cc
okrs is a skill published in the GitHub repository wdavidturner/product-skills (20 stars, last pushed 7mo ago), licensed MIT. It adds 105 tokens to every session and 1,094 once invoked, about $0.0005 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.