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 The-AI-Directory-Company/agents-and-skills --skill okr-writinggit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-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/the-ai-directory-company/agents-and-skills/okr-writing)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/okr-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/okr-writing/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/the-ai-directory-company/agents-and-skills/okr-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/okr-writing.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.00029 | $0.01711 |
| Opus 5 | $0.00015 | $0.00856 |
| Sonnet 5 | $0.00006 | $0.00342 |
| Haiku 4.5 | $0.00003 | $0.00171 |
Grade A, and why
okr-writing 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 8d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OKR Writing
Before you start
Gather the following from the user:
- What level are these OKRs for? (Company, department, team, individual)
- What time period? (Quarterly is standard; annual for company-level only)
- What are the company or department OKRs? (Team OKRs must align upward)
- What was the outcome of last quarter's OKRs? (Scores, lessons, carryovers)
- How many objectives? (3-5 per level is the practical maximum)
If the user wants to write 8+ objectives, push back: "OKRs are about focus, not coverage. If everything is a priority, nothing is. Choose the 3-5 things that would make this quarter a success if you achieved nothing else."
OKR structure
Each OKR set follows this format:
OBJECTIVE: [Qualitative, inspiring, time-bound statement of what you want to achieve]
KR1: [Quantitative metric] from [baseline] to [target]
KR2: [Quantitative metric] from [baseline] to [target]
KR3: [Quantitative metric] from [baseline] to [target]
Objective rules
- Qualitative and motivating — describes a desired end state
- Ambitious but not impossible — should feel uncomfortable at 70% confidence
- Time-bound (implicitly by the OKR cycle, e.g., Q2 2025)
- No metrics in the objective — that is what Key Results are for
- Starts with a verb: "Establish," "Accelerate," "Reduce," "Build"
Key Result rules
- Quantitative and measurable — a number that can be verified
- States a baseline ("from") and target ("to")
- 2-5 Key Results per Objective
- Measures outcomes, not tasks — "Ship feature X" is a task, "Increase activation rate from 30% to 45%" is a Key Result
- Each KR is independently valuable — achieving 2 of 3 should still matter
OKR template
## Q2 2025 OKRs — [Team Name]
### Objective 1: [Verb + desired end state]
Alignment: Supports [Company/Dept Objective name or number]
| KR# | Key Result | Baseline | Target | Owner |
|-----|-------------------------------------------------|----------|--------|----------|
| 1.1 | [Metric description] | [X] | [Y] | @person |
| 1.2 | [Metric description] | [X] | [Y] | @person |
| 1.3 | [Metric description] | [X] | [Y] | @person |
### Objective 2: [Verb + desired end state]
Alignment: Supports [Company/Dept Objective name or number]
| KR# | Key Result | Baseline | Target | Owner |
|-----|-------------------------------------------------|----------|--------|----------|
| 2.1 | [Metric description] | [X] | [Y] | @person |
| 2.2 | [Metric description] | [X] | [Y] | @person |
| 2.3 | [Metric description] | [X] | [Y] | @person |
What ships with it
3 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.
- 8d ago First seen · 145 lines · 29 tokens per session scan A 54804b642292
okr-writing is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 1,711 once invoked, about $0.0001 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
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
innovation
Innovation management expertise for innovation frameworks (Design Thinking, Stage-Gate), ideation processes, innovation portfolio management, venture capital, open innovation, and IP strategy. Use when driving innovation, managing R&D portfolios, or building innovation programs.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.