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 alexclowe/awesome-claude-cowork-plugins --skill stakeholder-communicationgit clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-pluginsWrote 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/alexclowe/awesome-claude-cowork-plugins/stakeholder-communication)<a href="https://agentmods.dev/skills/alexclowe/awesome-claude-cowork-plugins/stakeholder-communication"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/stakeholder-communication/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/alexclowe/awesome-claude-cowork-plugins/stakeholder-communication"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-claude-cowork-plugins/stakeholder-communication.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.00019 | $0.00613 |
| Opus 5 | $0.00010 | $0.00307 |
| Sonnet 5 | $0.00004 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
stakeholder-communication 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- stakeholder-communication — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You understand how to communicate construction project information to different stakeholders effectively. When the user is preparing reports, correspondence, or meeting documentation, apply these principles automatically.
Owner communication
When communicating with project owners:
- Lead with the executive summary — owners want the big picture first
- Present schedule and budget status clearly with visual indicators (on track, at risk, behind)
- Translate construction terminology into business language: "We are 3 days behind on the critical path, which may push the completion date" not "Activity 2340 has negative float of 3 days"
- Frame problems with solutions: "The HVAC delivery is delayed 2 weeks. We have reschenced interior framing to absorb the delay without impacting the completion date"
- Be transparent about risks — surprises erode trust far more than bad news delivered proactively
- Include photos — visual progress is the most compelling status indicator
Subcontractor coordination
When communicating with subcontractors:
- Be specific about scope, schedule, and expectations
- Reference contract documents, drawing sheets, and specification sections explicitly
- For schedule coordination: provide look-ahead schedules with specific dates, not vague timelines
- For scope clarification: reference the specific contract exhibit, drawing detail, or specification section
- For backcharge or quality issues: document with photos, reference the contract standard, and provide clear corrective action requirements
- Maintain professional relationships — subcontractors are partners, not adversaries
RFI communication
For Requests for Information:
- Restate the question clearly before providing the response — this creates a complete record
- Reference specific drawings (sheet number, detail callout) and specifications (section number, paragraph)
- Provide definitive answers when possible — vague responses generate follow-up RFIs
- Note cost and schedule impacts of the response
- Track response times against contractual requirements (typically 5-10 business days)
- Route to the appropriate design team member when the question requires design interpretation
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.
- 12d ago First seen · 64 lines · 19 tokens per session scan A 4b99b34fa223
stakeholder-communication is a skill published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (26 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 613 once invoked, about $0.0001 per session on Opus 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-30.
Other skills, from other repositories
coordinate-meeting
Coordinates project meetings: generates a structured agenda, creates a Google Calendar event, and prepares a protocol template. Covers 5 meeting types across the full project lifecycle — tasks #6, #15, #17, #20, #26. Meeting types: Go/No-Go (Phase 1, #6), Client Demo (Phase 3, #15), Sprint Planning (Phase 4, #17)…
generate-change-impact
Generates a change impact assessment file (change-impact-CR-001.xlsx) for Phase 4 — Development. PM describes a scope change request; the agent classifies the change (scope / budget / timeline / resource), analyzes impact on project-plan.md and project-budget.xlsx, calculates timeline delta, budget delta, and risk…
generate-estimate
Generates a preliminary timeline and budget estimate for an IT project (Phase 1 — Initiation). Reads available project files (client questionnaire, project charter, constraints, team list), applies analogy-based estimation using built-in agent knowledge of typical IT projects, and produces a three-scenario (optimistic…
generate-approval-letter
Generates an approval-letter.md email body and an email-tpl-approval.md template for Phase 2 — Planning. Reads project-plan.md, project-budget.xlsx, and resource-plan.md to compose a formal approval request addressed to all Approver-level stakeholders from stakeholder-map.md. Produces two artifacts: the letter email…
generate-budget
Generates a detailed project budget (project-budget.xlsx) for Phase 2 — Planning, based on preliminary-estimate.xlsx and resource-plan.md. Produces a single baseline scenario structured by project phases and cost categories (team, infrastructure, GTM), with a contingency reserve as a separate line item. Covers task #9…
generate-questionnaire
A questionnaire builder for IT projects. It creates either a client questionnaire for gathering requirements at the start or a lessons-learned questionnaire for the team at the end, and can organize the answers.