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 agentmods add skills/craftos-dev/craftbot/task-plannernpx skills add CraftOS-dev/CraftBot --skill task-plannergit clone --depth 1 https://github.com/CraftOS-dev/CraftBotWrote 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/craftos-dev/craftbot/task-planner)<a href="https://agentmods.dev/skills/craftos-dev/craftbot/task-planner"><img src="https://agentmods.dev/badge/skills/craftos-dev/craftbot/task-planner.svg" alt="Measured on agentmods" 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.00033 | $0.01113 |
| Opus 5 | $0.00016 | $0.00557 |
| Sonnet 5 | $0.00007 | $0.00223 |
| Haiku 4.5 | $0.00003 | $0.00111 |
Grade A, and why
task-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 2d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Planner
Help users break down goals into actionable steps, organize tasks, and create realistic plans.
When to Use
- Starting a new project or goal
- Feeling overwhelmed by a large task
- Need to prioritize multiple tasks
- Planning events or activities
- Creating daily/weekly schedules
- Breaking down complex goals
Planning Process
Step 1: Define the Goal
Clarify:
- What is the end result you want?
- When does it need to be done?
- What resources do you have?
- What constraints exist?
Step 2: Break Down Into Tasks
- Identify major milestones - Key checkpoints toward the goal
- List all tasks - Everything that needs to happen
- Order by dependency - What must happen before what
- Estimate effort - How long each task takes
Step 3: Prioritize
Use the Eisenhower Matrix:
| Urgent | Not Urgent | |
|---|---|---|
| Important | Do First | Schedule |
| Not Important | Delegate | Eliminate |
Or MoSCoW Method:
- Must have - Critical, non-negotiable
- Should have - Important but not critical
- Could have - Nice to have
- Won't have - Out of scope for now
Step 4: Create the Plan
## Goal: [What you want to achieve]
### Timeline: [Start date] → [End date]
### Milestones
1. [Milestone 1] - [Target date]
2. [Milestone 2] - [Target date]
3. [Milestone 3] - [Target date]
### Task Breakdown
#### Phase 1: [Phase name]
- [ ] Task 1 (Est: X hrs)
- [ ] Task 2 (Est: X hrs)
- [ ] Task 3 (Est: X hrs)
#### Phase 2: [Phase name]
- [ ] Task 4 (Est: X hrs)
- [ ] Task 5 (Est: X hrs)
### Dependencies
- Task 2 requires Task 1 to be complete
- Phase 2 can't start until Milestone 1 is reached
### Risks & Mitigation
- [Risk 1]: [How to handle it]
- [Risk 2]: [How to handle it]
Planning Templates
Daily Planning
## Today: [Date]
### Top 3 Priorities
1. [Most important task]
2. [Second priority]
3. [Third priority]
### Other Tasks
- [ ] Task A
- [ ] Task B
- [ ] Task C
### Meetings/Appointments
- [Time]: [Event]
### Notes
[Anything to remember]
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.
- 2d ago First seen · 179 lines · 33 tokens per session scan A 53c33cf28170
task-planner is a skill published in the GitHub repository CraftOS-dev/CraftBot (380 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 1,113 once invoked, about $0.0002 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
turix-mac
Computer Use Agent (CUA) for macOS automation using TuriX. Use when you need to perform visual tasks on the desktop, such as opening apps, clicking buttons, or navigating UIs that don't have a CLI or API.
browser-control
Control web pages in an existing Chromium remote-debugging session with deterministic sagui commands or the browser-only AI Agent. Use when Claude Code needs to inspect tabs, observe semantic elements, navigate, click, type, send keys, scroll, or complete a browser goal through CDP without controlling native macOS UI…
macos-control
Control macOS GUI applications via mouse automation, keyboard input, screenshots, image recognition, and AppleScript execution. Use when you need to interact with macOS app UIs, take screenshots, click buttons, type text, scroll, drag, or locate images on screen.
open-record-replay
Record a user-demonstrated macOS workflow with the Open Record/Replay CLI, inspect the captured event stream, prepare a skill evidence package, and hand it to the host agent's native skill creator. Use when the user asks the agent to watch them perform a task, record a workflow, or create/refine a reusable Computer…
artifact-storage-policy
管理 Codex 交付物的專案識別、Google Drive/GitHub 路由、檔名、儲存位置與回讀驗證;凡工作報告、外部保存、交付成果或新 repository 選擇涉及遠端儲存時使用。.
model-worker-routing
Route a task to the existing Ox Alpha worker only when the user explicitly names Ox Alpha; preserve normal Codex behavior for all other tasks.