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 krillinai/growth-skills --skill growth-capacity-planninggit clone --depth 1 https://github.com/krillinai/growth-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/krillinai/growth-skills/growth-capacity-planning)<a href="https://agentmods.dev/skills/krillinai/growth-skills/growth-capacity-planning"><img src="https://agentmods.dev/badge/skills/krillinai/growth-skills/growth-capacity-planning/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/krillinai/growth-skills/growth-capacity-planning"><img src="https://agentmods.dev/badge/skills/krillinai/growth-skills/growth-capacity-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00084 | $0.02565 |
| Opus 5 | $0.00042 | $0.01282 |
| Sonnet 5 | $0.00017 | $0.00513 |
| Haiku 4.5 | $0.00008 | $0.00257 |
Grade A, and why
growth-capacity-planning 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 12d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth Capacity Planning
Turn growth demand and operating obligations into a versioned capacity record that exposes feasible service, constraints, contention, reserves, and conditional response options. Capacity is a unit-, time-, skill-, service-, and evidence-specific ability to complete accepted work reliably; it is not headcount, budget, access, quota, utilization, or theoretical maximum alone.
Read capacity-contract-and-units.md before accepting demand, workload, resource, calendar, state, unit, conversion, or numerical capacity. Read flow-constraints-and-service.md before using queues, WIP, throughput, lead time, Little's Law, utilization, bottlenecks, shared resources, service classes, or reserves. Read scenarios-governance-and-actions.md before building scenarios, transferring a plan across markets, using workforce data, selecting a gap response, or preparing an external handoff. Read output-contract.md before delivery. Use playbook-sources.md for the pinned Growth Playbook basis.
Select One Mode
| Mode | Use |
|---|---|
specification |
Define the capacity system and evidence requests before compatible demand or supply observations exist |
build |
Reconcile supplied demand, workload, resources, flow, obligations, scenarios, and decisions into one capacity plan |
audit |
Inspect an existing plan for false availability, incompatible units, double booking, hidden queues, unsafe utilization, weak evidence, or governance failure |
refresh |
Preserve the prior version and update affected capacity after material demand, supply, service, dependency, market, or operating change |
Name one primary mode. Use evidence-pending, reconciling, scenario-ready, decision-ready, blocked, approved-record, superseded, or expired as the record state. A state does not prove approval, availability, allocation, execution, delivery, customer outcome, or business impact.
What ships with it
5 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.
- 12d ago First seen · 86 lines · 84 tokens per session scan A 36df2a588734
growth-capacity-planning is a skill published in the GitHub repository krillinai/growth-skills (43 stars, last pushed 15d ago), licensed MIT. It adds 84 tokens to every session and 2,565 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.