okr-tree-modeling

okr-tree-modeling is a skill for Claude Code, Codex from event4u-app/agent-config. It costs 38 tokens per session (1,247 once invoked), scanned A, original, MIT.

A method for breaking a company objective into measurable team objectives and key results, or OKRs, that connect back to the larger goal.

In plain words
What is it for?
It is for creating, reviewing, and stress-testing OKR trees for a quarter, half-year, or year.
Why use it?
It exposes vague goals, vanity measures, orphan results, and results that do not clearly support a parent objective.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for creating, reviewing, and stress-testing OKR trees for a quarter, half-year, or year.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/event4u-app/agent-config/okr-tree-modeling
Install

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.

Any agent
npx skills add event4u-app/agent-config --skill okr-tree-modeling
Clone the repo
git clone --depth 1 https://github.com/event4u-app/agent-config

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for okr-tree-modeling

README.md
[![agentmods](https://agentmods.dev/badge/skills/event4u-app/agent-config/okr-tree-modeling/github.svg)](https://agentmods.dev/skills/event4u-app/agent-config/okr-tree-modeling)
Your own site
<a href="https://agentmods.dev/skills/event4u-app/agent-config/okr-tree-modeling"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/okr-tree-modeling/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.

agentmods 80×15 button for okr-tree-modeling

Your own site · 80×15
<a href="https://agentmods.dev/skills/event4u-app/agent-config/okr-tree-modeling"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/okr-tree-modeling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,247 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.01247
Opus 5 $0.00019 $0.00624
Sonnet 5 $0.00008 $0.00249
Haiku 4.5 $0.00004 $0.00125

Measured 8d ago against content hash 657014b48ced, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

okr-tree-modeling 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.

src/skills/okr-tree-modeling/SKILL.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

okr-tree-modeling

When to use

  • A leadership team wrote a quarterly objective and needs three measurable KRs that actually move it.
  • A draft OKR tree needs review for orphan KRs, vanity metrics, or KRs that ladder to two parents.
  • A team-level OKR set needs to be checked against the company objective it claims to serve.

Do NOT use for ranking competing initiatives within one OKR — that's prioritization, not decomposition (route elsewhere — see Related Skills).

Procedure

Step 0: Inspect

  1. Identify the cognition cluster. OKR-as-strategy lives near the CEO/COO; OKR-as-PM-tool lives near the head of product. The decomposition mechanic is the same; the ladder-up target differs.
  2. Confirm timeframe (quarter / half / year) — KR cadence depends on it.

Step 1: Lock the parent objective

  1. Restate the parent in one sentence with a verb of change (grow, reduce, ship, win) and an outcome — not an output.
  2. Bad: "Improve onboarding." Good: "Reduce time-to-first-value for new accounts to under 7 days."
  3. If the parent has no verb of change or no outcome, the tree is built on sand. Stop and rewrite the parent.

Step 2: Decompose into 3 KRs

  1. Each KR must satisfy four tests: (a) measurable end-state, (b) the team owns the lever, (c) achievable iff the parent is achieved, (d) failing it should be visibly bad.
  2. Three is the floor and the ceiling. One KR makes the objective brittle; five dilutes ownership.
  3. Anti-pattern: "ship X feature" as a KR. Shipping is an output. The KR is what changes when the feature lands.

Step 3: Cascade to team-level

  1. For each company KR, define 2–3 team-level KRs that, taken together, achieve the parent KR — not duplicate it.
  2. Anti-pattern: copy-paste the parent KR with a smaller number ("60% of company KR is 30% for our team"). Real cascades change shape — input metrics for some teams, leading indicators for others.
  3. Mark each team KR as trailing (lagging outcome — revenue, retention) or leading (input the team controls — activation rate, response time). A tree that is all-trailing is unactionable.

Read the full file on GitHub · 102 lines

Changes

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.

  1. 8d ago First seen · 102 lines · 38 tokens per session scan A 657014b48ced

Subscribe to this mod's changes

okr-tree-modeling is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 1,247 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-04.