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 alexgrebeshok-coder/ai-pmo-skills --skill forecast-enginegit clone --depth 1 https://github.com/alexgrebeshok-coder/ai-pmo-skillsWrote 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/alexgrebeshok-coder/ai-pmo-skills/forecast-engine)<a href="https://agentmods.dev/skills/alexgrebeshok-coder/ai-pmo-skills/forecast-engine"><img src="https://agentmods.dev/badge/skills/alexgrebeshok-coder/ai-pmo-skills/forecast-engine/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/alexgrebeshok-coder/ai-pmo-skills/forecast-engine"><img src="https://agentmods.dev/badge/skills/alexgrebeshok-coder/ai-pmo-skills/forecast-engine.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.00061 | $0.02177 |
| Opus 5 | $0.00030 | $0.01089 |
| Sonnet 5 | $0.00012 | $0.00435 |
| Haiku 4.5 | $0.00006 | $0.00218 |
Grade A, and why
forecast-engine 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forecast Engine — Прогнозирование проекта
Назначение
Прогнозирование ключевых параметров проекта:
- Срок завершения (EAC Date)
- Итоговая стоимость (EAC Cost)
- Остаток работ (ETC)
- Сценарный анализ "что если"
- Вероятность завершения в срок/бюджет
Методы прогнозирования
1. EVM-based (Earned Value)
EAC (Estimate at Completion) — Прогноз итоговой стоимости:
| Метод | Формула | Когда использовать |
|---|---|---|
| Типичный | EAC = BAC / CPI | Текущая эффективность сохранится |
| Атипичный | EAC = AC + (BAC - EV) | Отклонение разовое, дальше по плану |
| Комбинированный | EAC = AC + (BAC - EV) / (CPI × SPI) | Отклонения и по срокам, и по стоимости |
ETC (Estimate to Complete) — Сколько осталось:
ETC = EAC - AC
2. Trend-based (По тренду)
Анализ скорости выполнения за последние N периодов:
Средняя скорость = Σ(Выполнено за период) / N периодов
Остаток работ = 100% - Текущий %
Прогноз завершения = Сегодня + (Остаток / Скорость)
3. Monte Carlo (Вероятностный)
Симуляция 1000+ сценариев с учётом:
- Разброса длительностей (оптимист/пессимист)
- Корреляции между задачами
- Вероятности рисков
Результат: распределение вероятностей завершения
Workflow
Шаг 1: Сбор данных
Из progress-tracker получаем:
- Плановые показатели (PV, BAC)
- Фактические показатели (EV, AC)
- Историю выполнения (тренд)
Шаг 2: Расчёт прогнозов
# Базовые расчёты EVM
BAC = 10_000_000 # Бюджет
AC = 4_800_000 # Фактические затраты
EV = 4_500_000 # Освоенный объём
CPI = EV / AC # 0.9375
SPI = EV / PV # 0.90
# Прогноз стоимости (типичный)
EAC = BAC / CPI # 10_666_667 ₽
# Прогноз остатка
ETC = EAC - AC # 5_866_667 ₽
# Отклонение от бюджета
VAC = BAC - EAC # -666_667 ₽ (перерасход)
Шаг 3: Прогноз сроков
# На основе SPI
плановый_срок = 180 # дней
прошло = 90 # дней
выполнено = 45% # по факту
# Прогноз при текущем темпе
оставшийся_срок = (100% - 45%) / (45% / 90 дней)
# = 55% / 0.5%/день = 110 дней
прогноз_завершения = сегодня + 110 дней
отклонение = (90 + 110) - 180 = +20 дней
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 · 249 lines · 61 tokens per session scan A aa34ac02b0fb
forecast-engine is a skill published in the GitHub repository alexgrebeshok-coder/ai-pmo-skills (10 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 2,177 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.