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 resource-allocatorgit 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/resource-allocator)<a href="https://agentmods.dev/skills/alexgrebeshok-coder/ai-pmo-skills/resource-allocator"><img src="https://agentmods.dev/badge/skills/alexgrebeshok-coder/ai-pmo-skills/resource-allocator/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/resource-allocator"><img src="https://agentmods.dev/badge/skills/alexgrebeshok-coder/ai-pmo-skills/resource-allocator.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.02518 |
| Opus 5 | $0.00030 | $0.01259 |
| Sonnet 5 | $0.00012 | $0.00504 |
| Haiku 4.5 | $0.00006 | $0.00252 |
Grade A, and why
resource-allocator 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 9d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resource Allocator — Распределение ресурсов
Назначение
Оптимальное распределение ресурсов между проектами:
- Персонал (бригады, специалисты)
- Техника (экскаваторы, самосвалы, краны)
- Материалы
- Анализ загрузки и выявление конфликтов
Типы ресурсов
Трудовые ресурсы
| Категория | Единица | Целевая загрузка |
|---|---|---|
| ИТР | чел.-день | 85-95% |
| Рабочие | чел.-смена | 80-90% |
| Бригады | бригадо-смена | 75-85% |
Техника
| Категория | Единица | Целевая загрузка |
|---|---|---|
| Экскаваторы | маш.-час | 75-85% |
| Самосвалы | маш.-час | 80-90% |
| Краны | маш.-час | 60-70% |
| Бульдозеры | маш.-час | 70-80% |
Материалы
| Категория | Управление |
|---|---|
| Основные материалы | Just-in-time, минимальный запас |
| Критичные материалы | Страховой запас 2-4 недели |
| Расходные | Постоянный запас |
Workflow
Шаг 1: Инвентаризация ресурсов
Создаём реестр доступных ресурсов:
resources:
personnel:
- name: "Бригада №1 (земляные работы)"
type: brigade
capacity: 8 # человек
skills: [excavation, grading]
base_location: "База Салехард"
availability: 100%
- name: "Бригада №2 (бетонные работы)"
type: brigade
capacity: 6
skills: [concrete, formwork, reinforcement]
base_location: "База Салехард"
availability: 100%
equipment:
- name: "Экскаватор Hitachi ZX200"
type: excavator
capacity: 200 # м³/смена
location: "Объект Мост №5"
availability: 85%
- name: "Автокран КС-55713"
type: crane
capacity: 25 # тонн
location: "База"
availability: 100%
Шаг 2: Сбор потребностей
Из gantt-planner получаем:
- Какие работы запланированы
- Когда и какие ресурсы нужны
- Объёмы и длительности
requirements:
- project: "Мост №5"
task: "Устройство опор"
period: "01.02 - 28.02.2026"
needs:
- type: brigade
skill: concrete
quantity: 2
- type: crane
capacity: ">20т"
quantity: 1
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.
- 9d ago First seen · 273 lines · 61 tokens per session scan A fc1f5c6c4888
resource-allocator 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,518 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.