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 sponsor-roadmapgit 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/sponsor-roadmap)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/sponsor-roadmap"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/sponsor-roadmap/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/sponsor-roadmap"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/sponsor-roadmap.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.00050 | $0.01021 |
| Opus 5.5 | $0.00020 | $0.00408 |
| Sonnet 5.5 | $0.00010 | $0.00204 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
sponsor-roadmap 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sponsor Roadmap
When to use
Build a phase-aligned plan of sponsor visibility, actions, and asks — tuned to binding readiness constraints, not generic "executive support."
What this skill does not do
- Does not write comms copy — route message drafting to
/change-management:communications-plan. - Does not assign sponsor — assumes named sponsor exists; flags if missing.
- Does not replace steering governance — major go/no-go stays with program forums.
Preconditions
| Input | If missing |
|---|---|
| Program phases or milestones | Ask timeline; infer from roadmap if provided |
| Practice profile sponsor definitions | Use visible/available/active defaults; [PROVISIONAL] |
| Readiness assessment (recommended) | Build generic roadmap; flag untargeted asks |
Provisional mode
Without named sponsor: produce role-based roadmap; flag [review] — cannot calibrate to individual capacity.
Trust spine
- Confidence bands (
narrative-synthesis):- High: Each checkpoint traces to readiness gap or phase gate; asks are specific and doable.
- Medium: Phases clear; some asks generic pending readiness input.
- Low: Sponsor unnamed or phases unstated — scaffold only.
- Failure modes:
- Analytical rigor: Every ask must be observable — "support the change" is not an action.
- Strategic advice vs. support: Sponsor chooses which asks to accept; roadmap presents options.
Workflow
-
Read practice profile — sponsor visibility definitions, cadence, escalation path.
-
If readiness assessment exists, anchor high-priority checkpoints to binding constraint response (e.g. sponsor floor walk before go-live if frontline able-risk).
-
Map program phases — launch, build, pilot, go-live, sustain, reinforce (or user's labels from transformation roadmap).
-
For each phase, define:
- Visibility — what the organization must see the sponsor do (town hall, video, site visit — per profile).
- Availability — office hours, escalation path, decision turnaround.
- Active removal of blockers — specific decisions or resource calls only the sponsor can make.
- Ask of sponsor — time-bound, observable, tied to a segment or dimension.
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 · 106 lines · 50 tokens per session scan A acf3ae79811f
sponsor-roadmap is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 1,021 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
review
Run the full pre-merge panel: parallel audit and lens reviewers over a diff, consolidated into one severity-ranked verdict.
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.
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.
debate
Settle a go/no-go on one risky change against an alternative through an advocate, a skeptic, and a neutral investigator.