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 steering-packgit 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/steering-pack)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/steering-pack"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/steering-pack/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/steering-pack"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/steering-pack.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.00052 | $0.01660 |
| Opus 5.5 | $0.00021 | $0.00664 |
| Sonnet 5.5 | $0.00010 | $0.00332 |
| Haiku 4.5 | $0.00005 | $0.00166 |
Grade A, and why
steering-pack 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Steering Pack
When to use
Steering committee deck outline — decisions first, escalation-filtered risks, action titles, appendix for detail.
What this skill does not do
- Does not fabricate status — use
status-reportor verified inputs. - Does not present full RAID — escalation threshold only in live deck.
- Does not pad without decisions — shorten pack if none pending.
Preconditions
| Input | If missing |
|---|---|
| Org + pmo profiles | Tag [PROVISIONAL] |
RAID + milestones or existing status-report |
Skeleton with INPUT NEEDED |
| Time budget | Ask; default 60 min [PROVISIONAL] |
Provisional mode
[PROVISIONAL] — monthly cadence; generic escalation thresholds.
Trust spine
- Confidence bands (
narrative-synthesis):- High: Decisions lead; risks filtered; action titles; time budget respected or bloat flagged.
- Medium: Status derived from partial inputs with gaps listed.
- Low: No inputs — skeleton only.
- Failure modes:
- Accountability gap: Each decision slide has explicit Ask.
- Escalation triggers: Pack exceeds time budget — BLOAT FLAG.
Purpose
Produce a steering pack where decisions come first and status supports them — filtered to escalation thresholds, action-titled slides, and an appendix for detail the room shouldn't sit through.
Precondition: load profiles
Before building the pack, read both:
~/.claude/plugins/config/claude-for-strategy/org-profile.md~/.claude/plugins/config/claude-for-strategy/pmo/CLAUDE.md
If missing or template, surface practice setup bounce with /pmo:practice-setup or "provisional".
Provisional mode
Defaults: monthly steering cadence; escalation = items with program-level schedule impact or unresolved >30 days; generic RAG thresholds. Tag [PROVISIONAL].
Workflow
Step 1: Orient
| Question | Answer |
|---|---|
| Meeting | Steering committee name, date if known |
| Time budget | Total minutes — drives agenda weighting |
| Decisions pending | List or "derive from inputs" |
| Inputs available | RAID, milestones, prior status-report, decision log |
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 · 202 lines · 52 tokens per session scan A 512c35929f5d
steering-pack is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 1,660 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
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.
task-decomposition
Breaks features into atomic, independently verifiable tasks. No task should take more than 4 hours. Unblocks parallel work and reduces integration risk.