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-change-impactgit 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-change-impact)<a href="https://agentmods.dev/skills/kirkruglov/claude-project-manager/generate-change-impact"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-project-manager/generate-change-impact/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-change-impact"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-project-manager/generate-change-impact.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.00154 | $0.02172 |
| Opus 5 | $0.00077 | $0.01086 |
| Sonnet 5 | $0.00031 | $0.00434 |
| Haiku 4.5 | $0.00015 | $0.00217 |
Grade A, and why
generate-change-impact 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 11d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: generate-change-impact
Generates a change impact assessment for Phase 4 — Development (task #21).
PM describes the change request; the agent classifies it, analyzes impact on
timeline and budget, calculates deltas and risk level. Output: change-impact-{id}.xlsx.
Mode B: agent prepares draft, PM makes the decision.
Triggers
Russian: «запрос на изменение скоупа», «оценка изменения», «влияние изменения на проект», «изменение скоупа», «CR по проекту», «оцени изменение», «изменение требований», «корректировка скоупа» English: "scope change request", "change impact assessment", "generate change impact", "change request analysis", "evaluate scope change", "change order impact"
Language Detection
Determine the language of the user's request:
- If the request is in Russian → use templates with
-rusuffix, respond in Russian - Otherwise → use templates with
-ensuffix, respond in English
Input
| Data | Required | Source |
|---|---|---|
| Change description | yes | PM writes in chat |
| Request ID (CR-001, etc.) | no | PM provides or agent assigns next in sequence |
| Requester | no | PM provides or leave blank |
| Project plan | no | 02-planning/project-plan.md — deadlines and tasks |
| Project budget | no | 02-planning/project-budget.xlsx — budget items |
Output
| File | Project path | Format | Description |
|---|---|---|---|
change-impact-{id}.xlsx |
04-development/ |
.xlsx | Change impact assessment |
File structure — 2 sheets (Summary, Impact Detail) — defined in templates/change-impact-{lang}.md.
Instructions
Step 1 — Validate Request
Guard-rail — check request type. If the request concerns general change management (methodology, processes) or does not describe a specific scope change → respond: "generate-change-impact assesses the impact of a specific scope change request. Describe the specific change: what needs to change, the rationale, and the expected impact. The skill will produce a structured assessment for decision-making." 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.
- 11d ago First seen · 232 lines · 154 tokens per session scan A 125c63da25f3
generate-change-impact is a skill published in the GitHub repository KirKruglov/claude-project-manager (6 stars, last pushed 4mo ago), licensed MIT. It adds 154 tokens to every session and 2,172 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
estimate
A development-estimation tool that analyzes project plans or source code and creates an Excel estimate grouped by development, labor, cloud, API, and miscellaneous costs.
super-claudio:productivity
Productivity and document creation skill. Use when the user wants to create documents, presentations, spreadsheets, dashboards, or needs help with planning and organization tools. Trigger on: "create a presentation", "make slides", "write a report", "create a PDF", "build a dashboard", "make a spreadsheet", "organize…
sn-da-excel-workflow
A step-by-step workflow for analysing Excel workbooks with multiple sheets. It covers reading data, cleaning it, filtering and combining results, and exporting reports, with a separate strategy for large files.
sn-da-large-file-analysis
A workflow for analyzing very large Excel datasets, especially files with at least 10,000 rows. It uses lower-memory reading, streaming through rows, splitting work into chunks, and converting data to Parquet, a column-based data format suited to repeated analysis.
category-filtering-and-difficulty-analysis
A workflow for grouping Excel records into categories and analyzing them across several measures, including text length and terminology density.
excel-multi-sheet-dynamic-analysis
A workflow for analyzing Excel workbooks with multiple sheets by finding relevant headers and fields, cleaning data, comparing sheets, and creating visual summaries.