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 agentmods add skills/kirkruglov/claude-project-manager/monitor-progressnpx skills add KirKruglov/claude-project-manager --skill monitor-progressgit 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/monitor-progress)<a href="https://agentmods.dev/skills/kirkruglov/claude-project-manager/monitor-progress"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-project-manager/monitor-progress.svg" alt="Measured on agentmods" 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.00146 | $0.03437 |
| Opus 5 | $0.00073 | $0.01718 |
| Sonnet 5 | $0.00029 | $0.00687 |
| Haiku 4.5 | $0.00015 | $0.00344 |
Grade A, and why
monitor-progress 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 5d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: monitor-progress
Monitors project execution across 6 modes — from sprint progress tracking to stream synchronization and final data collection. Reads Jira, project-plan, and project-budget. Generates structured reports; triggers email notifications for deviations and weekly status. Falls back gracefully when Jira is unavailable.
Triggers
Russian: «проверь прогресс», «статус проекта», «отчёт по прогрессу», «еженедельный отчёт», «проверь отклонения», «отклонения по срокам/бюджету», «синхронизация потоков», «собери фактические данные», «данные для закрытия» English: "check progress", "project status", "progress report", "weekly status", "check deviations", "deviation report", "sync streams", "collect actual data", "closing data"
Language Detection
- Request in Russian → templates
*-ru.md, all outputs in Russian - Otherwise → templates
*-en.md, all outputs in English
Modes
| Mode | Task | Phase | Trigger type | Output |
|---|---|---|---|---|
progress-report |
#18 | 4 | command | progress-report-{date}.md |
deviation-check |
#19 | 4 | command / schedule (daily) | deviation-report-{date}.md + email E4 |
sync-streams |
#25 | 5 | command / schedule (weekly Mon, phase 5 only) | sync-report-{date}.md + email E5 |
actual-data |
#28 | 6 | command | actual-data-report.xlsx (schema) |
weekly-status |
Р1 | 3–5 | scheduled (Mon 9:00) | weekly-status-{date}.md + email E7 |
daily-deviation |
Р2 | 3–5 | scheduled (Mon–Fri 9:00) | daily-deviation-{date}.md |
Input
| Data | Required | Source |
|---|---|---|
| Mode (explicit or inferred) | yes | PM in chat or scheduled task prompt |
| project-state.md | yes | project root |
| project-plan.md | yes (most modes) | 02-planning/ |
| project-budget.xlsx | for deviation/closure | 02-planning/ |
| Jira sprint data | preferred | Jira MCP (fallback: PM provides manually) |
| Stream reports (sync-streams) | yes | reports/ — latest progress-report-*.md |
| All Jira data (actual-data) | yes | Jira MCP (fallback: PM provides) |
What ships with it
15 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.
- templates/actual-data-report-schema.md 5.8 KB
- templates/deviation-report-template-en.md 2.0 KB
- templates/deviation-report-template-ru.md 3.0 KB
- templates/email-tpl-deviation-deadline-en.md 1.7 KB
- templates/email-tpl-deviation-deadline-ru.md 2.7 KB
- templates/email-tpl-deviation-sync-en.md 1.7 KB
- templates/email-tpl-deviation-sync-ru.md 2.9 KB
- templates/email-tpl-weekly-status-en.md 1.9 KB
- templates/email-tpl-weekly-status-ru.md 2.9 KB
- templates/progress-report-template-en.md 1.7 KB
- templates/progress-report-template-ru.md 2.3 KB
- templates/sync-report-template-en.md 2.7 KB
- templates/sync-report-template-ru.md 4.3 KB
- templates/weekly-status-template-en.md 2.1 KB
- templates/weekly-status-template-ru.md 3.1 KB
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.
- 5d ago First seen · 264 lines · 146 tokens per session scan A d8594d6cee65
monitor-progress is a skill published in the GitHub repository KirKruglov/claude-project-manager (6 stars, last pushed 4mo ago), licensed MIT. It adds 146 tokens to every session and 3,437 once invoked, about $0.0007 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
powerpoint-cli
PowerPoint CLI automation skill for Windows presentations. Use when a coding agent needs token-efficient, scriptable, or unattended PowerPoint automation via pptcli commands. Best for CI/CD, scheduled jobs, batch processing, PowerShell workflows, and bulk deck edits. Supports slides, shapes, text frames, tables…
github-flow-for-claude-on-web
Complete GitHub workflow for Claude Code on the web. ALL GitHub operations MUST use REST API (never gh CLI). Includes branch naming (claude/-sessionId), push retry logic, PR/issue management via API, and complete workflows. Use for all GitHub interactions in Claude Code web environment.
self-testing
E2E self-testing workflow for vibing.nvim using a separate Neovim instance controlled over RPC. Use when writing or debugging E2E tests, running npm run test:e2e, or executing the 3-try auto-fix rule after implementing a feature. Covers the…
vibing-orchestrate
Run several independent tasks in parallel by creating worker vibing.nvim chats, handing each one a self-contained brief, and aggregating their results. Use when the user asks for parallel work ("do these three in parallel", "split this across separate chats", "並行でやって", "この2つを別々のチャットで").
test-design
Automatically design comprehensive E2E test cases for newly implemented vibing.nvim features. Use immediately after completing feature implementation (Phase 5.4) and before running E2E tests. Generates test scenarios covering Happy paths, Error cases, Edge cases, and Integration points with priority ranking…
vibing-chat-search
Use when the user wants to find a past vibing.nvim conversation by topic — phrases like "前に〜について聞いたことあったっけ", "did we talk about X before", "find that chat where I asked about Y". Searches every chat file under .vibing/chat/ (both User and Assistant content) for a natural-language query, narrows candidates with grep…