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 build-strategy-mapgit 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/build-strategy-map)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/build-strategy-map"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/build-strategy-map/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/build-strategy-map"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/build-strategy-map.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.00073 | $0.02445 |
| Opus 5.5 | $0.00029 | $0.00978 |
| Sonnet 5.5 | $0.00015 | $0.00489 |
| Haiku 4.5 | $0.00007 | $0.00245 |
Grade A, and why
build-strategy-map 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Strategy Map
When to use
For strategy office, FP&A, or ops excellence practitioners building or refreshing a balanced scorecard strategy map. Assumes familiarity with BSC vocabulary; output is a structured draft for strategist review, not a board-ready conclusion.
Use when candidate objectives exist and need causal linkage across perspectives — the intellectual core of a scorecard, not objectives sorted into four boxes.
What this skill does not do
- Does not set perspective order — run
/balanced-scorecard:define-perspectivesfirst if no agreed top-of-chain exists. - 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 UNVALIDATED links for
/balanced-scorecard:review-and-validate; does not invent causal prose to make the map look complete. - Does not cascade to BU/team scorecards — use
/balanced-scorecard:cascade-to-scorecards.
Preconditions
| Input | If missing |
|---|---|
Perspective order (from define-perspectives or practice profile) |
Halt — route to /balanced-scorecard:define-perspectives; a map without an agreed causal top is building on sand |
| Candidate objectives or themes to structure | Ask for them; do not draft objectives from thin air without labeling output as scaffold-only |
Practice profile (~/.claude/plugins/config/claude-for-strategy/balanced-scorecard/CLAUDE.md) |
Proceed with labeled assumptions from org-profile.md; flag [review] on sector/top-perspective choices |
Provisional mode
When inputs are thin (objectives named but mechanisms unstated, or perspective order assumed not confirmed):
- Label output CONFIDENCE: structured first pass — never defensible recommendation.
- Tag every unstated mechanism UNVALIDATED — no mechanism stated; do not supply plausible-sounding causal prose.
- List missing inputs explicitly in STRUCTURAL FLAGS.
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 · 197 lines · 73 tokens per session scan A c1f3bcd6b23d
build-strategy-map is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 3mo ago), licensed MIT. It adds 73 tokens to every session and 2,445 once invoked, about $0.0003 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
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.