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 status-reportgit 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/status-report)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/status-report"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/status-report/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/status-report"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/status-report.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.00049 | $0.01841 |
| Opus 5.5 | $0.00020 | $0.00736 |
| Sonnet 5.5 | $0.00010 | $0.00368 |
| Haiku 4.5 | $0.00005 | $0.00184 |
Grade A, and why
status-report 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status Report
When to use
Audience-specific RAG status report from RAID and milestones — BLUF first; sponsor vs steering vs team calibration.
What this skill does not do
- Does not fabricate RAID/milestone status —
INPUT NEEDEDskeleton only. - Does not replace steering pack — route to
/pmo:steering-packfor governance deck. - Does not RAG-wash — profile thresholds required.
Preconditions
| Input | If missing |
|---|---|
| Org + pmo profiles | Tag [PROVISIONAL]; bounce to practice-setup |
| RAID log (open items) | Stop — ask; skeleton with INPUT NEEDED only |
| Milestone status | Stop — ask; skeleton with INPUT NEEDED only |
| Audience | Ask once; default sponsor with [PROVISIONAL] |
Provisional mode
[PROVISIONAL] — generic RAG thresholds; confirm audience.
Trust spine
- Confidence bands (
narrative-synthesis):- High: BLUF, profile RAG rules quoted, sourced RAID/milestones, Red/Amber action+ask.
- Medium: Partial inputs; structured first pass with gaps listed.
- Low: Missing RAID and milestones — skeleton only, no fake Green.
- Failure modes:
- Incentive Gaming: Guards RAG-washing — vague "on track" without thresholds.
- Escalation triggers: Red workstream — explicit ask in BLUF.
Purpose
Produce a status report the intended reader can act on in two minutes (sponsor) or use for working-level triage (team) — grounded in actual RAID and milestone inputs, not plausible-sounding fabrication.
Precondition: load profiles
Before drafting, 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: RAG = Green / Amber / Red with generic thresholds (Red = missed critical milestone or unresolved blocker >2 weeks; Amber = at risk within 2 weeks; Green = on track); audiences = sponsor, steering, working team. Tag [PROVISIONAL]. Ask user to confirm audience if not stated.
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 · 209 lines · 49 tokens per session scan A 2921334e8171
status-report is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 1,841 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.