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 serejaris/kimi-skills --skill gantt-plannergit clone --depth 1 https://github.com/serejaris/kimi-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/serejaris/kimi-skills/gantt-planner)<a href="https://agentmods.dev/skills/serejaris/kimi-skills/gantt-planner"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/gantt-planner/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/serejaris/kimi-skills/gantt-planner"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/gantt-planner.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.00070 | $0.01631 |
| Opus 5 | $0.00035 | $0.00816 |
| Sonnet 5 | $0.00014 | $0.00326 |
| Haiku 4.5 | $0.00007 | $0.00163 |
Grade A, and why
gantt-planner 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gantt-planner -- Interactive Gantt Chart & Critical Path Analysis
Automatically performs Critical Path Method (CPM) analysis on task lists and their dependencies, generating interactive HTML Gantt charts. Supports zooming, critical path filtering, hover details, and dependency arrow visualization.
Quick Start
Simplest usage — pass JSON directly:
python3 scripts/gantt_generator.py --json '{
"project": "New Product Launch",
"tasks": [
{"id": "T1", "name": "Requirements Analysis", "duration": 5, "dependencies": []},
{"id": "T2", "name": "UI Design", "duration": 4, "dependencies": ["T1"]},
{"id": "T3", "name": "Backend Development", "duration": 8, "dependencies": ["T1"]},
{"id": "T4", "name": "Frontend Development", "duration": 6, "dependencies": ["T2"]},
{"id": "T5", "name": "Integration Testing", "duration": 3, "dependencies": ["T3", "T4"]},
{"id": "T6", "name": "Deployment", "duration": 2, "dependencies": ["T5"]}
]
}' --output gantt.html
Read from a file with a specified start date:
python3 scripts/gantt_generator.py --file tasks.json --start-date 2026-05-01 --output gantt.html
Methodology: Critical Path Method (CPM)
Core Concepts
| Term | Abbreviation | Meaning |
|---|---|---|
| Earliest Start | ES | The earliest point at which a task can begin |
| Earliest Finish | EF | The earliest point at which a task can be completed (ES + Duration) |
| Latest Start | LS | The latest a task can start without delaying the project |
| Latest Finish | LF | The latest a task can finish without delaying the project |
| Total Float | TF | LS − ES; the number of days a task can be delayed |
| Critical Path | — | The sequence of tasks with zero float, determining the project's minimum duration |
Calculation Steps
- Topological Sort: Order tasks by dependencies, detecting any circular references
- Forward Pass: Starting from the initial tasks, compute ES and EF for each task
ES = max(EF of all predecessors)EF = ES + Duration
- Backward Pass: Working back from the final tasks, compute LS and LF
LF = min(LS of all successors)LS = LF - Duration
- Identify the Critical Path: Tasks where float (LS − ES) equals 0 form the critical path
What ships with it
2 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.
- 9d ago First seen · 152 lines · 70 tokens per session scan A 9b56e0086d0c
gantt-planner is a skill published in the GitHub repository serejaris/kimi-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 1,631 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-09-03.
Other skills, from other repositories
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
implement-improvements
Validate improvements from .turbo/improvements.md, recommend a working set tailored to what's in the backlog, and run one lane: direct fixes, investigation, or planned work. One lane per session. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
create-issue
Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue", "open an issue", "submit an issue", "report a bug", "file a bug report", "file a feature request", or "file a design proposal".
pick-next-issue
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".