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 OneWave-AI/claude-skills --skill okr-generatorgit clone --depth 1 https://github.com/OneWave-AI/claude-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/onewave-ai/claude-skills/okr-generator)<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/okr-generator"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/okr-generator/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/onewave-ai/claude-skills/okr-generator"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/okr-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00064 | $0.00820 |
| Opus 5 | $0.00032 | $0.00410 |
| Sonnet 5 | $0.00013 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
okr-generator 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OKR Generator
Generate a comprehensive, actionable okr-plan.md from user inputs, applying the Google/Intel OKR framework.
Contents
references/methodology.md-- Core OKR principles (non-negotiable rules to apply).references/inputs.md-- The four required inputs plus optional context.references/output-template.md-- Exact structure of the generatedokr-plan.md.references/best-practices.md-- Appendix content (common mistakes, OKR cycle, grading by KR type, reading list).
Workflow
- Read
references/inputs.md. Collect the four required inputs: company goals, team function, quarter/period, current metrics/baseline. If any are missing, ask for them. Never fabricate baselines. - Read
references/methodology.mdand apply every core principle. Objectives are qualitative and inspirational (no numbers); key results are quantitative and measurable (always a number). - Design 3-5 objectives. Attach 3-4 key results to each. Mark each as Committed or Aspirational, targeting roughly 60-70% committed and 30-40% aspirational across the plan.
- Map every objective to at least one company goal. Build both the alignment table and the cascade diagram. Drop any objective that does not ladder up.
- Write a 5-level scoring rubric (0.0, 0.3, 0.5, 0.7, 1.0) for every key result, with KR-specific descriptions.
- List initiatives separately from key results. Initiatives are the activities ("how"); key results are the measured outcomes ("what"). Never conflate them.
- Document dependencies and risks. Assign a single owner role to every objective and key result.
- Define the tracking cadence (weekly check-in, monthly scoring, quarterly retrospective) and include all three templates plus the appendix from
references/best-practices.md. - Generate the full document per
references/output-template.mdasokr-plan.mdin the working directory (or a user-specified path). Produce at least 400 substantive lines, no filler. - Summarize the plan: objective count and committed/aspirational split, the most ambitious key result, key dependencies/risks, and the recommended first action.
What ships with it
4 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.
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 · 46 lines · 64 tokens per session scan A f1c58488621e
okr-generator is a skill published in the GitHub repository OneWave-AI/claude-skills (291 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 820 once invoked, about $0.0003 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
after-action-report
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event.…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
mass-ulw
Drives dependency-ordered child work through the native workflow tool, one run per phase with retry/amend/send recovery. Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others.
beta-program-management
Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional…
okr-design
OKR design as actually shipped, not as conference-talk theory. Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration, and the difference between sandbagged OKRs (always 100%) and aspirational OKRs (always 30%) and stretch OKRs (genuine ambition…
roadmap-planning
Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next…