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-copilot-cowork-plugins --skill stakeholder-communicationgit clone --depth 1 https://github.com/alexclowe/awesome-copilot-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-copilot-cowork-plugins/stakeholder-communication)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/stakeholder-communication"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-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-copilot-cowork-plugins/stakeholder-communication"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-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.5 | $0.00008 | $0.00245 |
| Sonnet 5.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 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.
This is a copy
100% identical to stakeholder-communication — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 64 lines · 19 tokens per session scan A 4b99b34fa223
stakeholder-communication is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (21 stars, last pushed 16d ago), licensed MIT. It adds 19 tokens to every session and 613 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to stakeholder-communication, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
run-task
Execute a single Todo task through In Progress to Review, meeting every acceptance criterion with tests and vibe-lint checks. Refuses Planning-status tasks. Invoked as /agiflow:run-task . Uses gettask, updatetask, createtaskcomment.
blueprint
Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation…
agent-phase-closeout
A Chinese-language process for closing out a completed work stage and recording its state. It summarizes finished work, preserves decisions, freezes completed interfaces, and writes a resume checkpoint.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
google-workspace-ops
Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.
carrier-relationship-management
Codified expertise for managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships. Informed by transportation managers with 15+ years experience. Includes scorecarding frameworks, RFP processes, market intelligence, and…