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 KirKruglov/claude-project-manager --skill generate-comm-plangit clone --depth 1 https://github.com/KirKruglov/claude-project-managerWrote 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/kirkruglov/claude-project-manager/generate-comm-plan)<a href="https://agentmods.dev/skills/kirkruglov/claude-project-manager/generate-comm-plan"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-project-manager/generate-comm-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/kirkruglov/claude-project-manager/generate-comm-plan"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-project-manager/generate-comm-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.00153 | $0.02739 |
| Opus 5 | $0.00077 | $0.01370 |
| Sonnet 5 | $0.00031 | $0.00548 |
| Haiku 4.5 | $0.00015 | $0.00274 |
Grade A, and why
generate-comm-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 10d 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
98% identical to generate-comm-plan — 14 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
generate-comm-plan
Triggers
Russian: «сформируй план коммуникаций», «подготовь comm-plan», «кому и как коммуницировать» English: "generate comm plan", "create communication plan", "build comm plan"
Language Detection
Determine the language of the user's request:
- If the request is in Russian → use templates with
-rusuffix - Otherwise → use templates with
-ensuffix
All output (headings, labels, comments, instructions) must match the detected language.
1. Inputs
| Data | Required | Source | Notes |
|---|---|---|---|
| Project charter | yes | knowledge or chat | Source of stakeholders (section 5 "Team and Roles"), goals, scope, constraints |
| Project plan | yes | knowledge or chat | Source of milestones, phases, work blocks — for binding communications to events |
| Stakeholder data | no | chat or knowledge | Additional stakeholders not listed in the charter. In P1 — stakeholder-map.md |
| Channel preferences | no | chat | Communication channels used by the team (Slack, Teams, Email, Meets, etc.) |
If required data is missing — request it (system-prompt-draft.md §3.2):
To generate the communication plan, the following are needed:
— Project charter (project-charter.md) — source of team, goals, constraints
— Project plan (project-plan.md) — source of milestones and phases
Available: [list what is present].
Missing: [be specific].
If the project plan does not yet exist — respond: "The communication plan depends on the project plan. Recommend running generate-project-plan first."
2. Execution Algorithm
- Validate inputs. Check for charter + project plan. If missing → request using the template from §1. Do NOT generate a placeholder plan — respond ONLY with the data request.
- Extract stakeholders from charter. From section 5 "Team and Roles" + section 1 "Goal" (client, sponsor). Add from project context: external stakeholders (customers, contractors, legal, finance) if mentioned in constraints, risks, or scope.
- Build preliminary stakeholder list. For each: role, influence rating (H/M/L), interest rating (H/M/L), strategy (per matrix in §3). Mark ratings as agent assumptions.
- Show preliminary list to user. Format:
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 243 lines · 153 tokens per session scan A c963e802d2d8
generate-comm-plan is a skill published in the GitHub repository KirKruglov/claude-project-manager (6 stars, last pushed 4mo ago), licensed MIT. It adds 153 tokens to every session and 2,739 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to generate-comm-plan, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
litigation-workflow
Civil litigation workflow expertise — case management, deposition prep, evidence chain, and Federal Rules of Evidence.
construction-management
Estimating, scheduling, building codes, safety protocols, permitting, and project controls.
stakeholder-communication
Owner reports, subcontractor coordination, RFI responses, and meeting documentation.
run-team-retrospective
Use when a team needs to reflect on a completed period, project, or significant event — to extract what worked, what didn't, and what specific changes to make before the next cycle, rather than repeating the same patterns.
project-manager
This skill has been upgraded with agentic AI capabilities, OKR/KPI integration patterns, and async-first workflows based on 2026 PM best practices research.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.