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 cascade-to-scorecardsgit 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-to-scorecards)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/cascade-to-scorecards"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/cascade-to-scorecards/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/cascade-to-scorecards"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/cascade-to-scorecards.svg" alt="Reviewed on agentmods" width="80" 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.00061 | $0.01655 |
| Opus 5.5 | $0.00024 | $0.00662 |
| Sonnet 5.5 | $0.00012 | $0.00331 |
| Haiku 4.5 | $0.00006 | $0.00166 |
Grade A, and why
cascade-to-scorecards 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 1mo 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cascade to Scorecards
When to use
For strategy office or BU leaders translating a corporate strategy map into business-unit or team scorecards. Assumes a corporate map exists from /balanced-scorecard:build-strategy-map. Output is a structured cascade draft for strategist review.
What this skill does not do
- Does not build the corporate strategy map — requires
build-strategy-mapoutput first. - Does not set quarterly OKRs — if OKR plugin is layered beneath BSC per practice profile, route execution commitments to
/okr:cascade. - Does not select measures or targets — route to
/balanced-scorecard:select-measuresand/balanced-scorecard:set-targets-and-initiatives. - Does not validate empirical truth of mechanisms — flags weak or missing mechanisms; hand off to
/balanced-scorecard:review-and-validate.
Preconditions
| Input | If missing |
|---|---|
Corporate strategy map (from build-strategy-map or practice profile location) |
Halt — cannot cascade without a parent map |
| Target BU/team name and scope | Ask before drafting |
| Practice profile cascade policy (levels, local-objective policy) | Read profile; if absent, ask whether local-only objectives are expected and flag [review] |
Provisional mode
When corporate map is partial or BU scope is unclear:
- Label output as scaffold-only in CASCADE HEALTH CHECK.
- Flag coverage gaps explicitly; do not invent cascaded objectives to fill gaps.
- Tag mechanisms UNVALIDATED when the user cannot state how the BU operationalizes the corporate parent.
Trust spine
- Confidence bands (
structured-aggregation):- High: Every relevant corporate objective has a specific cascaded child with stated mechanism; local-only objectives explicitly flagged; coverage gaps listed.
- Medium: Mostly complete; some mechanisms weak or generic cascade partially flagged.
- Low: Scaffold only — missing parent map, fully generic or fully disconnected without deliberate call; explicitly marked incomplete.
- Tag vocabulary:
[verify],[review],UNVALIDATED,local, not tracedper pluginCLAUDE.md. - Failure modes:
- Strategic advice vs. support: Surfaces cascade structure and health flags; does not decide whether a BU should be autonomous vs. fully aligned —
[review]on fully disconnected patterns. - Client confidentiality: Cascade content may expose BU strategy — apply CONFIDENTIAL header; destination check before distribution.
- Accountability gap: CASCADE HEALTH CHECK and COVERAGE GAPS force engagement; generic copy-paste cascades flagged, not smoothed over.
- Analytical Rigor: N/A — mechanism discipline inherited from
build-strategy-map, not MECE decomposition here. - Incentive Gaming: N/A — no scoring or target-setting in this skill.
- Strategic advice vs. support: Surfaces cascade structure and health flags; does not decide whether a BU should be autonomous vs. fully aligned —
- Escalation triggers:
- Fully disconnected cascade with no deliberate autonomy rationale → flag and ask strategist to confirm intentional design.
- Fully generic cascade (copy-paste corporate objectives) → flag, require local operational specificity or explicit demotion.
- Corporate objective relevant to BU with zero cascaded support → name in COVERAGE GAPS; do not silently omit.
- OKR plugin installed and user expects quarterly KRs here → clarify seam; route to
/okr:cascade.
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.
- 1mo ago First seen · 131 lines · 61 tokens per session scan A 27c4bafcfa76
cascade-to-scorecards is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 1,655 once invoked, about $0.0002 per session on Opus 5.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
to-tickets
Slice a spec or a ticket into tracer-bullet tickets with blocking edges, published through the repo's tracker: .specs/tickets/ .md by default.
to-spec
Turn the settled conversation into a spec (PRD), published through the repo's tracker: .specs/specs/ .md by default.
setup
Configure this repo's issue tracker for the flow skills: GitHub, Jira, or local markdown (the default).
meeting-notes-to-tasks
Converts unstructured meeting notes into structured, assigned, time-bounded action items. Never leave a meeting without knowing who does what by when.
loom-usage
Meta-orchestration skill for Claude driving loom itself.
nx-monorepo
Provides comprehensive Nx monorepo management guidance for TypeScript/JavaScript projects. Use when creating Nx workspaces, generating apps/libraries/components, running affected commands, setting up CI/CD, configuring Module Federation, or implementing NestJS backends within Nx.