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 risk-analyzergit 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/risk-analyzer)<a href="https://agentmods.dev/skills/alexgrebeshok-coder/ai-pmo-skills/risk-analyzer"><img src="https://agentmods.dev/badge/skills/alexgrebeshok-coder/ai-pmo-skills/risk-analyzer/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/risk-analyzer"><img src="https://agentmods.dev/badge/skills/alexgrebeshok-coder/ai-pmo-skills/risk-analyzer.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.00065 | $0.02558 |
| Opus 5 | $0.00032 | $0.01279 |
| Sonnet 5 | $0.00013 | $0.00512 |
| Haiku 4.5 | $0.00006 | $0.00256 |
Grade A, and why
risk-analyzer 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Risk Analyzer — Анализ рисков проекта
Назначение
Комплексный анализ рисков строительных проектов:
- Идентификация рисков по категориям
- Оценка вероятности и влияния
- Построение матрицы рисков
- Разработка стратегий митигации
- Мониторинг триггеров рисков
Категории рисков
1. Технические риски
- Ошибки в проектной документации
- Несоответствие геологии проекту
- Технологические сложности
- Качество материалов
2. Организационные риски
- Нехватка квалифицированного персонала
- Проблемы с субподрядчиками
- Сбои в логистике
- Коммуникационные проблемы
3. Финансовые риски
- Рост цен на материалы
- Задержки финансирования
- Валютные колебания
- Банкротство контрагентов
4. Внешние риски
- Погодные условия (критично для ЯНАО)
- Изменения законодательства
- Действия заказчика
- Форс-мажор
5. Контрактные риски
- Неточности в договоре
- Изменение объёмов работ
- Претензии заказчика
- Штрафные санкции
Методология оценки
Шкала вероятности
| Уровень | Значение | Описание |
|---|---|---|
| 1 | Очень низкая | <10%, редко случается |
| 2 | Низкая | 10-30%, иногда случается |
| 3 | Средняя | 30-50%, периодически |
| 4 | Высокая | 50-70%, часто случается |
| 5 | Очень высокая | >70%, почти наверняка |
Шкала влияния
| Уровень | Значение | По срокам | По бюджету |
|---|---|---|---|
| 1 | Незначительное | <1 неделя | <5% |
| 2 | Небольшое | 1-2 недели | 5-10% |
| 3 | Умеренное | 2-4 недели | 10-20% |
| 4 | Значительное | 1-2 месяца | 20-40% |
| 5 | Критическое | >2 месяцев | >40% |
Матрица рисков
Влияние
5 │ 5 10 15 20 25
4 │ 4 8 12 16 20
3 │ 3 6 9 12 15
2 │ 2 4 6 8 10
1 │ 1 2 3 4 5
└──────────────────────
1 2 3 4 5 Вероятность
🟢 1-4: Низкий риск (мониторинг)
🟡 5-9: Средний риск (план митигации)
🟠 10-15: Высокий риск (активное управление)
🔴 16-25: Критический риск (немедленные действия)
Workflow
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 · 241 lines · 65 tokens per session scan A 0c5f749b20f4
risk-analyzer is a skill published in the GitHub repository alexgrebeshok-coder/ai-pmo-skills (10 stars, last pushed 6mo ago), licensed MIT. It adds 65 tokens to every session and 2,558 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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.