aod.okrs

A quarterly OKR document generator. OKRs, or Objectives and Key Results, pair a goal with measurable results used to track progress.

In plain words
What is it for?
Use it to create an OKR template for a selected quarter, reuse relevant product context, and send the document through product-manager approval.
Why use it?
It provides a consistent place to define quarterly goals and aligns them with an existing roadmap or product vision when available.

Command for Claude Code

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.

agentmods
npx agentmods add commands/davidmatousek/agentic-oriented-development-kit/aod.okrs
Clone the repo
git clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kit

Made for: Claude Code.

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,284 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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 $0.00013 $0.01284
Opus 5 $0.00006 $0.00642
Sonnet 5 $0.00003 $0.00257
Haiku 4.5 $0.00001 $0.00128

Measured 2d ago against content hash b471f281fd60, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

aod.okrs 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 2d 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.

Origin

This is a copy

100% identical to aod.okrs — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/aod.okrs.md · 186 lines

How it starts

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

User Input

$ARGUMENTS

Consider user input before proceeding (if not empty).

Overview

Scaffolds a quarterly OKR (Objectives and Key Results) document in docs/product/06_OKRs/ with a PM sign-off gate.

Flow: Determine quarter → Scaffold OKR template → PM sign-off → Write file

Step 1: Determine Quarter

  1. Parse current date to determine the quarter:
    • Jan-Mar → Q1
    • Apr-Jun → Q2
    • Jul-Sep → Q3
    • Oct-Dec → Q4
  2. Format as YYYY-QN (e.g., 2026-Q1)
  3. If $ARGUMENTS contains a quarter override (e.g., 2026-Q2), use that instead
  4. Check if docs/product/06_OKRs/{quarter}.md already exists
    • If exists: Use AskUserQuestion with options: View existing, Create with suffix (v2), Abort

Step 2: Gather Context (Optional)

  1. If docs/product/03_Product_Roadmap/ contains a roadmap for the same quarter, read it for alignment context
  2. If docs/product/01_Product_Vision/product-vision.md exists, read mission statement for objective alignment
  3. Store as context for template population hints

Step 3: Scaffold OKR Document

Build the OKR document with standard template:

---
okrs:
  quarter: {YYYY-QN}
  created: {YYYY-MM-DD}
  status: Draft
  review_date: null
triad:
  pm_signoff: null  # Populated after review
---

# {{PROJECT_NAME}} OKRs — {YYYY-QN}

**Quarter**: {QN} {YYYY}
**Status**: Draft
**Created**: {YYYY-MM-DD}
**Review Date**: [Schedule end-of-quarter review]

## Objective 1: [Qualitative Goal]

**Why This Matters**: [Alignment with product vision]

### Key Result 1.1: [Measurable Outcome]
- **Baseline**: [Starting value]
- **Target**: [End of quarter goal]
- **Current**: —
- **Status**: Not Started
- **Owner**: [Team member]

### Key Result 1.2: [Measurable Outcome]
- **Baseline**: [Starting value]
- **Target**: [End of quarter goal]
- **Current**: —
- **Status**: Not Started
- **Owner**: [Team member]

## Objective 2: [Qualitative Goal]

**Why This Matters**: [Alignment with product vision]

### Key Result 2.1: [Measurable Outcome]
- **Baseline**: [Starting value]
- **Target**: [End of quarter goal]
- **Current**: —
- **Status**: Not Started
- **Owner**: [Team member]

### Key Result 2.2: [Measurable Outcome]
- **Baseline**: [Starting value]
- **Target**: [End of quarter goal]
- **Current**: —
- **Status**: Not Started
- **Owner**: [Team member]

---

## Progress Tracking

**Week of [Date]**:
- KR 1.1: [Update]
- KR 1.2: [Update]
- KR 2.1: [Update]
- KR 2.2: [Update]

**Risks**:
- [Identified risks to OKR achievement]

**Actions**:
- [ ] [Action items to address risks]

---

## Scoring Guide

At end of quarter, score each Key Result:
- **1.0**: Fully achieved
- **0.7**: Strong progress, nearly there
- **0.4**: Some progress, but short of target
- **0.0**: No meaningful progress

**Target average**: 0.6–0.7 (stretch goals should be ambitious)

Read the full file on GitHub · 186 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. 2d ago First seen · 186 lines · 13 tokens per session scan A b471f281fd60

Subscribe to this mod's changes

aod.okrs is a command published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 1,284 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to aod.okrs, differing in 0 lines, and is treated as a copy.