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 sananthanarayan/skilldrop --skill okr-cascadegit clone --depth 1 https://github.com/sananthanarayan/skilldropWrote 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/sananthanarayan/skilldrop/okr-cascade)<a href="https://agentmods.dev/skills/sananthanarayan/skilldrop/okr-cascade"><img src="https://agentmods.dev/badge/skills/sananthanarayan/skilldrop/okr-cascade.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.00081 | $0.01648 |
| Opus 5 | $0.00041 | $0.00824 |
| Sonnet 5 | $0.00016 | $0.00330 |
| Haiku 4.5 | $0.00008 | $0.00165 |
Grade A, and why
okr-cascade 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
okr-cascade
Turns company objectives into team OKRs that actually roll up — and surfaces what a cascade usually hides: the objectives nobody credibly owns (the gap registry) and the KRs that count activity instead of causing outcomes (the causal metric tree). Org-level counterpart to success-metrics, which owns feature-level measurement — this skill decides what the teams aim at; success-metrics designs how one feature proves it moved a KR.
How to respond
-
Get the company OKRs and the cycle. From the input or by asking (at most 2 questions, spent on: "what are the company's top 3–5 objectives this cycle, verbatim?" and "which teams are in scope?"). Record company OKRs verbatim — rewriting the company's words without saying so corrupts the roll-up. No company objectives exist at all → stop; that's a strategy conversation (
strategy-analysis), not a cascade. Non-interactive run (no user to ask): an unstated cycle or team list gets assumed and tagged[assumption]; absent company OKRs are never invented — emitBLOCKED: need the company OKRs, verbatim — rerun with the top 3–5 objectives, their KRs, and the teams in scopeinstead. -
Grade the company KRs before cascading them. Each company KR is either an outcome (a customer or business result: retention, revenue, time-to-value) or an output (a thing shipped: "launch v2", "migrate to k8s"). Outputs at company level get flagged with the outcome they presumably serve — ✅ "'Launch self-serve onboarding' → presumably serves activation rate; recommend restating as the activation target". Cascading an output produces teams that hit every KR while the business stands still.
-
Derive team OKRs per company objective. For each in-scope team: an objective (qualitative, motivating, this-cycle) and 2–4 KRs that are (a) measurable at the team's scope — the team's work moves the number without needing three other teams to also succeed; (b) causally upstream of a company KR, with the causal sentence written out: ✅ "Cut p95 checkout latency to 800ms — slow checkout is the top named cause of cart abandonment
[data: support tags], which feeds company KR 'checkout conversion +2pp'"; (c) scored 0.0–1.0 at cycle end — a KR that can only be "done/not done" is a task wearing a KR's clothes. Not every team maps to every objective — forcing it manufactures alignment theater; a team with no credible contribution to an objective simply doesn't appear under it.
What ships with it
4 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.
- 7d ago First seen · 60 lines · 81 tokens per session scan A 74f0d6711e80
okr-cascade is a skill published in the GitHub repository sananthanarayan/skilldrop (2 stars, last pushed 23d ago), licensed MIT. It adds 81 tokens to every session and 1,648 once invoked, about $0.0004 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
readme
This skill should be used to audit OR elevate the README of a public repository. Trigger with "improve the README", "make the readme high quality", "elevate this readme", "audit the readme", "add badges", "is our README good", or before publishing/releasing a repo. Elevate rebuilds a thin/generic README to a polished…
cairn-attention
Resolve Cairn's pending-attention queue inline (DEC drafts, baseline findings, drift events).
cairn-direction
Spec-tightener + subagent dispatcher. Engage on code-change asks — verbs, bug reports, observations. Pivot-aware on active tasks.
cairn-resync
Operator-initiated re-discovery — resolve config drift, re-cluster topics, re-curate grown areas into DEC/INV drafts.
ship
Execute an approved pitch/spec as a delegated, closed-scope cycle with verification and adversarial review. Invoke it yourself with /ship — a cycle spawns a writer and opens a PR, so it starts when you say so. Enforces the execution playbook: right-size gate, pre-spawn filter, doc-bundle, PR format, review.
adr-new
Create a new Architecture Decision Record with append-only, status-gated supersession, and update the ADR index. Invoke with /adr-new, or let /tdd-author invoke it on approval of an ADR action (this skill stays model-invocable for that reason).