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 daddia/claude-for-strategy --skill cascadegit clone --depth 1 https://github.com/daddia/claude-for-strategyWrote 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/daddia/claude-for-strategy/cascade)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/cascade"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/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.00063 | $0.01163 |
| Opus 5 | $0.00032 | $0.00581 |
| Sonnet 5 | $0.00013 | $0.00233 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cascade
When to use
OKR cycle owners cascading objectives/KRs down levels — with contribution, capacity, alignment, and cross-team conflict checks naive cascades skip.
What this skill does not do
- Does not draft objectives — route to
/okr:draft-objectives. - Does not write KRs — route to
/okr:write-key-results. - Does not set targets — route to
/okr:set-targets.
Preconditions
| Input | If missing |
|---|---|
| Parent objectives/KRs to cascade | Ask user to provide |
| Practice profile (cascade levels, ceilings) | Proceed with defaults (3–5 objectives, 2–5 KRs); flag [review] |
| Child-level draft objectives/KRs | Ask user to provide or offer to draft via other skills |
Provisional mode
Without org structure data: fan-out/capacity check labeled [review]; cross-team conflict check still runs on provided KRs.
Trust spine
- Confidence bands (
structured-aggregation):- High: MECE cascade coverage, contribution tests complete, conflicts named.
- Medium: Some restatements or coverage gaps flagged.
- Low: Parent KRs missing or child set incomplete — scaffold only.
- Failure modes:
- Strategic advice vs. support: Flags restatements and conflicts; does not resolve ownership disputes.
- Client confidentiality: OKR content may be internal-only — CONFIDENTIAL header.
- Accountability gap: Cross-team conflicts surfaced for conversation, not silently merged.
- Analytical Rigor: Contribution test MECE; orphans and uncovered parents listed.
- Incentive Gaming: Catches cross-team KR pairs that game one metric at another's expense.
- Escalation triggers: Overloaded fan-out on single parent KR — flag parent KR too broad.
Workflow
- Read the practice profile for cascade levels and objectives/KR ceilings.
- Run contribution test on every cascaded objective — does achieving it move the parent KR?
- Run restatement check — contribution vs. same goal with different owner.
- Run alignment/coverage check — orphaned KRs and uncovered parent KRs.
- Run fan-out/capacity check — too many children on one parent KR.
- Run cross-team conflict check — sibling KRs that improve one team at another's expense.
- Completeness check before output.
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 · 115 lines · 63 tokens per session scan A 20d06b982ff8
cascade is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 1,163 once invoked, about $0.0003 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
swarmclaw
AI agent runtime and multi-agent orchestration platform. Teaches agents how to use SwarmClaw's 6 primitive tools, persistent memory, dreaming, delegation, connectors, credentials, and the skill system. Use when an agent is running on SwarmClaw and needs to understand the platform's capabilities.
spec-herdr-review
Run visible multi-agent spec reviews in Herdr through interactive agent CLIs such as Claude, Codex, Copilot/GLM, or Grok/Composer. Supports two modes — a spec review (the design, before implementation) and an implementation review (the implemented diff vs the spec, after the calling model has built it). Ask for…
gpmc
Read-only Active Directory Group Policy inventory via LDAP — list GPOs, show OU/site links (enabled/disabled/enforced), find unlinked GPOs, search by name, and gpresult for the current user. Use when the user asks about GPOs, Group Policy, GPMC, linked vs unlinked policies, RSoP, what applies to this user, or runs…
claude-session
Find and inspect local Claude Code conversations by session GUID, title, phrase, or recent activity. Use when the user runs /claude-session, asks what Claude Code work they have been doing lately, says a Claude Code conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named…
grok-session
Find and inspect local Grok CLI conversations by session GUID, title, phrase, or recent activity. Use when the user runs /grok-session, asks what Grok work they have been doing lately, says a Grok conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named session, or wants to continue…
codex-session
Find and inspect local Codex task conversations, including by session GUID, title, recent activity, or a phrase from the conversation. Use when the user runs /codex-session, says a prior Codex conversation died or ran out of context, wants to resume a named task, asks what a local Codex task did, or wants to continue…