Paperclip is a Node.js server and React application for coordinating AI agents as a business team, with goals, organizational roles, budgets, governance, and work tracking in one interface. It is used by people managing multiple agents or autonomous agent organizations across tools such as OpenClaw, Claude Code, Codex, and Cursor. The catalogue includes skills, agents, an MCP add-on, and an instruction for working with Paperclip.
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 paperclipai/paperclip --skill task-planninggit clone --depth 1 https://github.com/paperclipai/paperclipWrote 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/paperclipai/paperclip/task-planning)<a href="https://agentmods.dev/skills/paperclipai/paperclip/task-planning"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/task-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/paperclipai/paperclip/task-planning"><img src="https://agentmods.dev/badge/skills/paperclipai/paperclip/task-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- 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.00032 | $0.00312 |
| Opus 5.5 | $0.00013 | $0.00125 |
| Sonnet 5.5 | $0.00006 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
task-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 17d 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
Task planning
Plan only as much as the work needs. If execution is authorized and the next step is small and clear, do it. A request for a plan alone does not require child tasks or a new approval gate.
Describe the intended outcome, relevant constraints, chosen approach, and how to verify success. Include uncertainties or decisions that affect execution. Use the user's preferred format; keep implementation steps within one owner's task unless another owner, useful parallel output, dependency, or independent review warrants separate work.
Save a requested plan as the issue document with key plan. Update its current
revision instead of duplicating it, and link the saved document in your response.
Use the native document tools when available; legacy agents follow the paperclip
skill's document and planning API mechanics.
Respect planning mode and explicit approval requests. When approval is required,
request confirmation of the latest plan revision and wait for that decision.
After acceptance, execute cohesive work on the current ordinary task. Use
paperclip-converting-plans-to-tasks when delegation is justified.
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.
- 17d ago Changed · -48 lines · -8 tokens per session 48d6501d6ef4
- 1mo ago First seen · 85 lines · 40 tokens per session scan A 9c52a44a30ec
task-planning is a skill published in the GitHub repository paperclipai/paperclip (106,591 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 312 once invoked, about $0.0001 per session on Opus 5.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
agent-swarm-issue
Agent skill for swarm-issue - invoke with $agent-swarm-issue.
agent-issue-tracker
Agent skill for issue-tracker - invoke with $agent-issue-tracker.
agent-project-board-sync
Agent skill for project-board-sync - invoke with $agent-project-board-sync.
agent-user-tools
Agent skill for user-tools - invoke with $agent-user-tools.
agent-swarm
Agent skill for swarm - invoke with $agent-swarm.
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…