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 communications-plangit 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/communications-plan)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/communications-plan"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/communications-plan/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/communications-plan"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/communications-plan.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.00977 |
| Opus 5.5 | $0.00020 | $0.00391 |
| Sonnet 5.5 | $0.00010 | $0.00195 |
| Haiku 4.5 | $0.00005 | $0.00098 |
Grade A, and why
communications-plan 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Communications Plan
When to use
Build a structured comms plan from stakeholder segments and program milestones — completeness and sequencing, not polished copy.
What this skill does not do
- Does not send comms — human approval per practice profile before external distribution.
- Does not replace brand/comms team — drafts structure; final voice and legal review stay with owners.
- Does not map stakeholders — route to
/change-management:stakeholder-impact-mapif audiences undefined.
Preconditions
| Input | If missing |
|---|---|
| Stakeholder segments or audience list | Ask or infer from scope; flag gaps |
| Key milestones (go-live, pilot, training) | Ask timeline |
| Practice profile comms approval path | Note default approval; [PROVISIONAL] |
Provisional mode
Without milestones: sequence by relative phase only (T-minus labels); flag dates as [TBD].
Trust spine
Structured-aggregation bands; every row has owner and approval note; no fabricated quotes from leadership.
Workflow
-
Read practice profile — comms ownership, approval path, channel preferences.
-
Use stakeholder impact map if available — audiences = segments plus any additional governance audiences (steering, unions, regulators).
-
For each milestone window, define comms rows:
- Audience — specific segment, not "all staff" unless truly universal.
- Message intent — what they need to know, feel, or do (not full copy).
- Channel — email, town hall, manager cascade, Slack, intranet — match segment reach from map.
- Timing — date or T-minus relative to milestone.
- Sender — who the audience must hear from (sponsor, manager, project, comms).
- Owner — who drafts.
- Approval — per profile path before send.
-
Sequencing checks:
- Managers hear before their teams when cascade model applies.
- "Why" before "what" before "how" for net-new change.
- No surprise go-live announcement without prior awareness row — flag violation.
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 · 102 lines · 50 tokens per session scan A d38a275d349a
communications-plan 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 977 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.