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-skills-kit --skill generate-closure-reportgit clone --depth 1 https://github.com/KirKruglov/claude-skills-kitWrote 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-skills-kit/generate-closure-report)<a href="https://agentmods.dev/skills/kirkruglov/claude-skills-kit/generate-closure-report"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-skills-kit/generate-closure-report/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-skills-kit/generate-closure-report"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-skills-kit/generate-closure-report.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.00050 | $0.03817 |
| Opus 5 | $0.00025 | $0.01909 |
| Sonnet 5 | $0.00010 | $0.00763 |
| Haiku 4.5 | $0.00005 | $0.00382 |
Grade A, and why
generate-closure-report 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- generate-closure-report — 97% identical, 9 lines differ
How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
generate-closure-report
Triggers
Russian: «сформируй отчёт о закрытии», «закрой проект», «подготовь closure report», «отчёт о закрытии проекта» English: "generate closure report", "close project", "project closure report", "prepare closure report"
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. Input Data
| Data | Required | Source | Notes |
|---|---|---|---|
| Project charter | yes | knowledge (project-charter.md) |
Goal, deliverables, team, sponsor, budget, timeline |
| Plan-fact report | yes | knowledge (plan-fact-report.md) |
Deviation summary, actual dates/budget/scope. If multiple files — use the latest by date |
| Lessons learned | yes | chat | User provides in any format: retrospective results, questionnaire answers, free text. Agent structures and assigns categories |
| Risk register | no | knowledge (risk-register.md) |
For section 4. If unavailable — agent asks the user about realized risks |
| Open items | no | chat | Tasks/questions remaining after closure. If not provided — replace section with "All items closed" |
| Lessons source | no | chat | team retrospective / questionnaire / PM input in chat. Default: PM input in chat |
If required data is missing — request it (system-prompt-draft.md §3.2):
To generate the project closure report, the following is needed:
1. Project charter (project-charter.md) — in knowledge or paste in chat.
2. Plan-fact report (plan-fact-report.md) — in knowledge or paste in chat.
3. Project lessons — in any format:
— team retrospective results;
— questionnaire answers;
— free-form description: what went well, what went wrong, what to do differently.
Available data: [list what is present].
Missing: [specify].
2. Execution Algorithm
What ships with it
4 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 · 274 lines · 50 tokens per session scan A 44dec39e23d2
generate-closure-report is a skill published in the GitHub repository KirKruglov/claude-skills-kit (18 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 3,817 once invoked, about $0.0003 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
github-issue-creator
Turn error logs, screenshots, voice notes, and rough bug reports into crisp, developer-ready GitHub issues with repro steps, impact, and evidence.
onboarding-planner
TRIGGER THIS when preparing for new hires, planning first-day/week/month activities, creating onboarding schedules, building 30-60-90 day plans, designing welcome programs, organizing training schedules, or setting up buddy/mentorship programs. Designs comprehensive, engaging onboarding experiences that accelerate…
performance-review-assistant
TRIGGER THIS when conducting performance reviews, writing manager feedback, creating self-assessments, building peer feedback, developing PIPs, creating development plans, or handling difficult performance conversations. Helps write constructive, specific, actionable feedback that develops performance and documents…
roadmap-builder
Build product roadmaps with quarterly planning, feature prioritization, dependency mapping, and stakeholder alignment. Create actionable roadmaps that communicate strategy and guide execution.
sprint-planning
Plan sprints with story point estimation, capacity planning, sprint goals, and retrospective frameworks. Organize teams for effective iteration with clear goals, realistic commitments, and continuous improvement.
onboarding-playbook
Design customer onboarding playbooks with milestone tracking, training plans, health checks, and success criteria.