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 kpi-tree-buildergit 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/kpi-tree-builder)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/kpi-tree-builder"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/kpi-tree-builder/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/kpi-tree-builder"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/kpi-tree-builder.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.00051 | $0.01082 |
| Opus 5.5 | $0.00020 | $0.00433 |
| Sonnet 5.5 | $0.00010 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
kpi-tree-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 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KPI Tree Builder
When to use
Decompose a North Star into MECE drivers and leading indicators — math or causal chain must work, not decorative strategy diagrams.
What this skill does not do
- Does not build spreadsheets — route to
/performance:tracker-builder. - Does not invent North Star definition — locks definition first or marks provisional.
- Does not set OKR targets — route to
/okr:set-targets.
Preconditions
| Input | If missing |
|---|---|
| Org + performance profiles | Tag [PROVISIONAL]; bounce to practice-setup |
| North Star metric name | Ask; halt decomposition until supplied |
| Relationship type (multiplicative/additive/causal) | Ask once |
Provisional mode
[PROVISIONAL] — no predefined North Star from profile; generic categories without house codes.
Trust spine
- Confidence bands (
structured-aggregation):- High: North Star locked; 3–5 MECE drivers; indicators with tight definitions and sources.
- Medium: Some
INPUT NEEDEDsources; double-counting flagged. - Low: North Star definition ambiguous — halt decomposition.
- Failure modes:
- Strategic advice vs. support: Tree is draft for analytics leadership review.
- Client confidentiality: Metric definitions may be sensitive — CONFIDENTIAL header.
- Accountability gap: Every indicator has owner or
INPUT NEEDED. - Analytical Rigor: MECE drivers; double-counting and lagging-only branches flagged.
- Incentive Gaming: Rejects decorative trees dressed as analysis.
- Escalation triggers: Math doesn't decompose — switch to causal chain explicitly or flag gap.
Workflow
Step 1: Orient
Read ## KPI taxonomy from performance profile. Confirm North Star, relationship type, audience, purpose, evidence pack.
Step 2: Definition lock
Confirm North Star formula, window, population, source, owner before decomposing.
Step 3: MECE driver decomposition
3–5 drivers that multiply, sum, or causally determine North Star.
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 · 130 lines · 51 tokens per session scan A 9d983a219ff2
kpi-tree-builder is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 1,082 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-09-03.
Other skills, from other repositories
review
Run the full pre-merge panel: parallel audit and lens reviewers over a diff, consolidated into one severity-ranked verdict.
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.
tdd
Test-driven development, from unit to end-to-end tests. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration or end-to-end tests (Playwright, Cypress). Don't use to backfill tests on existing code (/refactor) or diagnose an unknown bug (/debug).
visual-review
Two visual modes — render a PR diff as an HTML page with each hunk annotated by principle, or check a UI change in a real browser (screenshots, console, network). Use for a visual/HTML diff report, "check the UI", or "screenshot before/after". Don't use for text-only feedback (/code-review), unit tests (/tdd), or full…
to-pr
Gate, push, and open a GitHub pull request on the repo's PR template, then watch CI.
debate
Settle a go/no-go on one risky change against an alternative through an advocate, a skeptic, and a neutral investigator.