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-response-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-response-plan)<a href="https://agentmods.dev/skills/kirkruglov/claude-project-manager/generate-response-plan"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-project-manager/generate-response-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-response-plan"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-project-manager/generate-response-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.00167 | $0.02464 |
| Opus 5 | $0.00084 | $0.01232 |
| Sonnet 5 | $0.00033 | $0.00493 |
| Haiku 4.5 | $0.00017 | $0.00246 |
Grade A, and why
generate-response-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.
How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: generate-response-plan
Generates an incident response plan for Phase 5 — Launch. Supports Technical, Operational, and Business incident types. Classifies severity from PM description, reads project context files, and produces a structured response-plan-{id}.md. Mode B: agent prepares a draft, PM reviews and approves.
Triggers
Russian: «инцидент», «план реагирования», «произошёл инцидент», «сбой системы», «критическая ошибка», «проблема при запуске», «составь план реагирования», «что делать при инциденте» English: "incident response plan", "incident occurred", "system down", "generate response plan", "launch incident", "critical bug response", "production issue"
Language Detection
- Request in Russian → template
response-plan-ru.md, responses in Russian - Otherwise → template
response-plan-en.md, responses in English
Input
| Data | Required | Source |
|---|---|---|
| Incident description (what happened, when, where) | yes | PM in chat |
| Incident type and severity | no | Inferred from description or PM asked |
| Project name and current phase | no | project-state.md |
| Team composition and roles | no | 02-planning/resource-plan.md or project-state.md |
| Escalation contacts | no | 01-initiation/stakeholder-map.md |
| Current plan milestones | no | 02-planning/project-plan.md |
| Registered risks | no | 01-initiation/risk-register.md |
Output
| File | Project path | Task |
|---|---|---|
response-plan-{INCIDENT_ID}.md |
03-execution/ |
#27 |
Incident ID format: INC-YYYYMMDD-NNN (sequential within the project).
File name example: response-plan-INC-20260425-001.md
Instructions
Step 1 — Guard-rail and Gather Incident Data
Guard-rail — verify request type. If the request is about incident management methodology in general, not a specific incident in a running project → respond: "generate-response-plan creates an incident response plan for a specific incident in Phase 5 (Launch). Describe what happened in your project — I'll generate the plan." Do not start the workflow.
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 · 242 lines · 167 tokens per session scan A 812c67d19f57
generate-response-plan is a skill published in the GitHub repository KirKruglov/claude-project-manager (6 stars, last pushed 4mo ago), licensed MIT. It adds 167 tokens to every session and 2,464 once invoked, about $0.0008 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-31.
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.