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 agentmods add skills/ironyjk/strategy-frameworks/okrnpx skills add ironyjk/strategy-frameworks --skill okrgit clone --depth 1 https://github.com/ironyjk/strategy-frameworksWrote 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/ironyjk/strategy-frameworks/okr)<a href="https://agentmods.dev/skills/ironyjk/strategy-frameworks/okr"><img src="https://agentmods.dev/badge/skills/ironyjk/strategy-frameworks/okr.svg" alt="Measured on agentmods" 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.04993 |
| Opus 5 | $0.00022 | $0.02497 |
| Sonnet 5 | $0.00009 | $0.00999 |
| Haiku 4.5 | $0.00004 | $0.00499 |
Grade A, and why
okr 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 6d 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 — 391 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 OKR (Objectives and Key Results)
목표 설정과 실행을 연결하는 프레임워크. Andy Grove가 Intel에서 개발, John Doerr가 Google에 도입하여 세계적으로 확산.
핵심 철학: "아이디어는 쉽다. 실행이 전부다." — John Doerr
📐 OKR 해부학 (Anatomy)
OKR = Objective (목표, 무엇을) + Key Results (핵심 결과, 어떻게 측정할 것인가)
구조
Objective: [정성적이고 영감을 주는 목표]
├── KR1: [측정 가능한 핵심 결과] → 0.0 ~ 1.0
├── KR2: [측정 가능한 핵심 결과] → 0.0 ~ 1.0
└── KR3: [측정 가능한 핵심 결과] → 0.0 ~ 1.0
예시
Objective: 고객이 사랑하는 온보딩 경험을 만든다
├── KR1: 신규 사용자 7일 리텐션 40% → 70% 달성
├── KR2: 온보딩 완료율 25% → 60% 달성
└── KR3: 온보딩 관련 CS 문의 월 200건 → 50건 이하로 감소
Objective: 산업청소 시장에서 압도적 기술 리더십을 확보한다
├── KR1: Gerotto 장비 도입 후 신규 수주 5건 달성
├── KR2: 기술 제안서 수주율 30% → 55%로 향상
└── KR3: 고객 만족도 NPS 점수 60 → 80 달성
✍️ Objective 작성 규칙 (목표 작성법)
| 규칙 | 설명 | 좋은 예 | 나쁜 예 |
|---|---|---|---|
| 영감을 주는 (Inspiring) | 팀이 아침에 일어나고 싶게 만드는 | "업계 최고의 고객 경험을 만든다" | "고객 만족도를 올린다" |
| 정성적 (Qualitative) | 숫자는 KR에, 목표는 방향을 | "개발팀의 배포 속도를 혁신한다" | "배포 횟수를 주 3회로 늘린다" |
| 시간 제한 (Time-bound) | 보통 분기(Quarter) 단위 | "Q2에 ~를 달성한다" | 기한 없는 목표 |
| 실행 가능 (Actionable) | 팀이 직접 영향을 줄 수 있는 | "우리 팀의 코드 품질을 높인다" | "경쟁사가 시장에서 철수한다" |
| 간결 (Concise) | 한 문장, 누구나 외울 수 있는 | 1줄 | 3줄 이상의 장문 |
Objective 수: 조직/팀당 3~5개 (이상적으로 3개)
📊 Key Result 작성 규칙 (핵심 결과 작성법)
| 규칙 | 설명 | 좋은 예 | 나쁜 예 |
|---|---|---|---|
| 측정 가능 (Measurable) | 숫자로 표현 | "월 매출 5억 달성" | "매출을 늘린다" |
| 구체적 (Specific) | 모호함 없이 | "신규 고객 50사 확보" | "고객을 많이 확보" |
| 시간 제한 (Time-bound) | 분기 내 달성 기한 | "6월 말까지" | "언젠가" |
| 검증 가능 (Verifiable) | Yes/No 판정 가능 | "앱스토어 평점 4.5 이상" | "앱을 개선한다" |
| 결과 중심 (Outcome) | 산출물이 아닌 결과 | "이탈률 5% 감소" | "이탈 방지 기능 출시" |
Key Result 수: Objective당 2~5개 (이상적으로 3개)
점수 체계 (Scoring: 0.0 ~ 1.0)
| 점수 | 의미 | 해석 |
|---|---|---|
| 0.0 ~ 0.3 | 실패 (빨강) | 의미 있는 진전 없음 |
| 0.4 ~ 0.6 | 진행 중 (노랑) | 진전은 있으나 목표 미달 |
| 0.7 ~ 1.0 | 달성 (초록) | 목표 수준 도달 또는 초과 |
Aspirational OKR의 sweet spot은 0.6~0.7. 매번 1.0이면 목표가 너무 쉬운 것.
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.
- 6d ago First seen · 391 lines · 44 tokens per session scan A b8ceec3b9452
okr is a skill published in the GitHub repository ironyjk/strategy-frameworks (11 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 4,993 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-08-30.
Other skills, from other repositories
new-venture
This skill should be used when the user wants to start working on a new business idea, product, startup, or client engagement — e.g. "I have a new idea", "set up a new venture", "register a new client", "let's analyze this business", "ایده جدید دارم", "یه بیزینس جدید", "ونچر جدید بساز", "کلاینت جدید", "میخوام روی این…
ceo-skill
CEO decision-making advisor and strategic thinking partner. Use when users need help with executive-level decisions including strategy, resource allocation, risk assessment, competitive positioning, organizational design, M&A evaluation, crisis response, OKR/KPI setting, fundraising, stakeholder management, cognitive…
bill-gates
Agente que simula Bill Gates — cofundador da Microsoft, arquiteto da industria de software comercial, estrategista tecnologico global, investidor sistemico e filantropo baseado em dados.
apply-fast-follower-strategy
Use when deciding whether to pioneer a new product category or market first, or deliberately let competitors validate it before entering with superior execution — per Duan Yongping's 敢为天下后 ("dare to follow, not pioneer") principle.
design-kpi-dashboard
Use when building or redesigning a performance dashboard to track organizational, team, or product KPIs and support data-driven decisions.
gtm
This skill should be used when the user asks for go-to-market strategy, positioning, launch planning, channel strategy, pricing strategy, or messaging — e.g. "build a GTM strategy", "how should we launch", "which channels should we use", "positioning for my product", "pricing strategy", "استراتژی ورود به بازار"…