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 Dokkabei97/forged-claude-code --skill okr-buildergit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/okr-builder)<a href="https://agentmods.dev/skills/dokkabei97/forged-claude-code/okr-builder"><img src="https://agentmods.dev/badge/skills/dokkabei97/forged-claude-code/okr-builder.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.00038 | $0.01219 |
| Opus 5 | $0.00019 | $0.00609 |
| Sonnet 5 | $0.00008 | $0.00244 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
okr-builder 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 7d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OKR Builder - Objectives and Key Results
Overview
Creates well-structured OKRs that align teams around outcomes, not outputs. Good OKRs answer "where are we going?" (Objective) and "how do we know we're getting there?" (Key Results).
1. When to Apply
| Trigger | Behavior |
|---|---|
| Quarter planning | Full OKR creation workflow |
| "OKR", "quarterly goals" | Interactive OKR builder |
| Team alignment needed | Cross-team OKR cascade |
2. OKR Template
# OKRs — [Q1/Q2/Q3/Q4] [Year]
## Company Level
### Objective 1: [Inspirational, qualitative goal]
> Owner: CEO | Confidence: [High/Medium/Low]
| # | Key Result | Baseline | Target | Current | Status |
|---|-----------|----------|--------|---------|--------|
| KR1 | [Measurable outcome] | [start] | [target] | [now] | 🟢🟡🔴 |
| KR2 | [Measurable outcome] | [start] | [target] | [now] | 🟢🟡🔴 |
| KR3 | [Measurable outcome] | [start] | [target] | [now] | 🟢🟡🔴 |
**Key Initiatives:**
- [Initiative that drives KR1]
- [Initiative that drives KR2]
---
### Objective 2: [Second company objective]
...
3. Writing Rules
Objectives
- Qualitative: No numbers in objectives
- Inspirational: Should motivate the team
- Time-bound: Achievable within the quarter
- 3-5 per company: More = less focus
| Good Objective | Bad Objective |
|---|---|
| "Become the go-to tool for indie hackers" | "Get 10K users" (that's a KR) |
| "Deliver a delightful onboarding experience" | "Improve onboarding" (too vague) |
| "Build a sustainable revenue engine" | "Make money" (not inspirational) |
Key Results
- Quantitative: Must have a number
- Outcome-based: Measure results, not activities
- 2-5 per objective: Focused
- 70% stretch: Should be uncomfortable but not impossible
| Good Key Result | Bad Key Result |
|---|---|
| "Increase activation rate from 30% to 50%" | "Launch onboarding feature" (output, not outcome) |
| "Reduce churn from 8% to 4%" | "Talk to 20 customers" (activity) |
| "Achieve NPS of 50+" | "Send NPS survey" (activity) |
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.
- 7d ago First seen · 169 lines · 38 tokens per session scan A e5d772951162
okr-builder is a skill published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 1,219 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-31.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
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…
create-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.