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 Bevel-Software/Hexis --skill capacity-plangit clone --depth 1 https://github.com/Bevel-Software/HexisWrote 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/bevel-software/hexis/capacity-plan)<a href="https://agentmods.dev/skills/bevel-software/hexis/capacity-plan"><img src="https://agentmods.dev/badge/skills/bevel-software/hexis/capacity-plan/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/bevel-software/hexis/capacity-plan"><img src="https://agentmods.dev/badge/skills/bevel-software/hexis/capacity-plan.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.00052 | $0.00911 |
| Opus 5.5 | $0.00021 | $0.00364 |
| Sonnet 5.5 | $0.00010 | $0.00182 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
capacity-plan 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 6d 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.
This is a copy
91% identical to capacity-plan — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
capacity-plan
Names like
~~chator~~project trackermean whichever tool of that kind is connected: a tool in one of your Hexis plugins, or one your agent has itself. The knowledge base is this workspace's knowledge base in Hexis, plus any other docs tool that is connected. When a source is not connected, skip it and say what you could not check.
Analyze team capacity and plan resource allocation.
Usage
Ask your agent for the capacity-plan skill by name, or just describe the job and it will pick the skill up. Give it:
What I Need From You
- Team size and roles: Who do you have?
- Current workload: What are they working on? (Upload from project tracker or describe)
- Upcoming work: What's coming next quarter?
- Constraints: Budget, hiring timeline, skill requirements
Planning Dimensions
People
- Available headcount and skills
- Current allocation and utilization
- Planned hires and timeline
- Contractor and vendor capacity
Budget
- Operating budget by category
- Project-specific budgets
- Variance tracking
- Forecast vs. actual
Time
- Project timelines and dependencies
- Critical path analysis
- Buffer and contingency planning
- Deadline management
Utilization Targets
| Role Type | Target Utilization | Notes |
|---|---|---|
| IC / Specialist | 75-80% | Leave room for reactive work and growth |
| Manager | 60-70% | Management overhead, meetings, 1:1s |
| On-call / Support | 50-60% | Interrupt-driven work is unpredictable |
Common Pitfalls
- Planning to 100% utilization (no buffer for surprises)
- Ignoring meeting load and context-switching costs
- Not accounting for vacation, holidays, and sick time
- Treating all hours as equal (creative work ≠ admin work)
Output
## Capacity Plan: [Team/Project]
**Period:** [Date range] | **Team Size:** [X]
### Current Utilization
| Person/Role | Capacity | Allocated | Available | Utilization |
|-------------|----------|-----------|-----------|-------------|
| [Name/Role] | [hrs/wk] | [hrs/wk] | [hrs/wk] | [X]% |
### Capacity Summary
- **Total capacity**: [X] hours/week
- **Currently allocated**: [X] hours/week ([X]%)
- **Available**: [X] hours/week ([X]%)
- **Overallocated**: [X people above 100%]
### Upcoming Demand
| Project/Initiative | Start | End | Resources Needed | Gap |
|--------------------|-------|-----|-----------------|-----|
| [Project] | [Date] | [Date] | [X FTEs] | [Covered/Gap] |
### Bottlenecks
- [Skill or role that's oversubscribed]
- [Time period with a crunch]
### Recommendations
1. [Hire / Contract / Reprioritize / Delay]
2. [Specific action]
### Scenarios
| Scenario | Outcome |
|----------|---------|
| Do nothing | [What happens] |
| Hire [X] | [What changes] |
| Deprioritize [Y] | [What frees up] |
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.
- 6d ago First seen · 112 lines · 52 tokens per session scan A 0802b75dfb4e
capacity-plan is a skill published in the GitHub repository Bevel-Software/Hexis (115 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 911 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to capacity-plan, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
docs-governance
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
coordinator
Take over as coordinator of the current LangWatch drive: read the live state from disk (the lane roster, the newest handover, the shape counters), report it, then work the handover's next action by writing manifests and spawning lanes. Replaces pasting a brief out of a handover document - the state is read, never…
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.
tencent-meeting-mcp
A Tencent Meeting assistant for scheduling meetings and working with participants, recordings, transcripts, and AI-generated meeting notes.