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/nikuscs/codex-multitask/multitask-plannpx skills add nikuscs/codex-multitask --skill multitask-plangit clone --depth 1 https://github.com/nikuscs/codex-multitaskWhat 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 | $0.00017 | $0.00164 |
| Opus 5 | $0.00009 | $0.00082 |
| Sonnet 5 | $0.00003 | $0.00033 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
multitask-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 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.
What it actually says
Multitask Plan
Run the companion command directly. Do not inspect plugin source, scripts, or docs before running unless the user explicitly asks to debug the plugin.
Keep narration minimal: return the planned workers only. --workers means "up to this many workers", not exactly this many workers.
Run the splitter only and print the worker plan without spawning workers.
Examples:
node plugins/multitask/scripts/multitask-companion.mjs plan --workers 4 "Split the auth refactor into independent workers."
node plugins/multitask/scripts/multitask-companion.mjs plan --plan-file plan.md --workers 5 "Execute this plan."
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 · 20 lines · 17 tokens per session scan A 2a53be220968
multitask-plan is a skill published in the GitHub repository nikuscs/codex-multitask (4 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 164 once invoked, about $0.0001 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
stop-that-shit
Keep coding agents focused on requested and necessary work. Use for bounded changes, review-only tasks, scope creep, speculative hardening, unnecessary hashing or dependencies, repeated audit loops, or when the user invokes Stop That Shit.
map-auto
Single-entry autonomous autopilot: routes a task through the existing MAP workflows via routetask, then drives the selected chain (map-plan -> map-efficient -> map-check -> map-review, as routed) end-to-end to a committed feature branch in one session, auto-approving routine workflow-control holds and hard-stopping on…
map-resume
Resume an interrupted MAP workflow from .map/ /stepstate.json checkpoint. Use when returning after context exhaustion, /clear, or a session crash mid-workflow. Do NOT use to start new work; use map-plan or map-efficient.
map-skill-eval
Evaluate a /map- skill's trigger accuracy and cost. Use when asked to measure skill trigger accuracy, run an eval-set, or check token/duration cost via mapify skill-eval. Do NOT use to plan or implement; use map-plan or map-efficient.
skills-management
Search, find, discover, install, remove, update, review, deduplicate, list, move, optimise, and iterate on skills for AI coding agents. Use when user asks "find a skill for X", "install skill", "remove skill", "update skills", "list skills", "deduplicate skills", "why are two skills shown", "choose the canonical…
agents-consilium
Run external coding agents (Codex, Claude Code, OpenCode, native Grok Build, Gemini) as independent reviewers, stateful repository researchers, or single-agent implementers. Use for multi-model opinions and code review, steerable Grok research, full-access delegation, long-running work, or reattaching to delegated…