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 arctan303/creator.skill --skill dev-plannergit clone --depth 1 https://github.com/arctan303/creator.skillWrote 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/arctan303/creator.skill/dev-planner)<a href="https://agentmods.dev/skills/arctan303/creator.skill/dev-planner"><img src="https://agentmods.dev/badge/skills/arctan303/creator.skill/dev-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/arctan303/creator.skill/dev-planner"><img src="https://agentmods.dev/badge/skills/arctan303/creator.skill/dev-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.00033 | $0.00477 |
| Opus 5.5 | $0.00013 | $0.00191 |
| Sonnet 5.5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
dev-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 7d 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
开发计划
Purpose
让另一会话能从有效契约、前置成果和验收继续执行，计划规模与任务相称。
Trigger
用户要求计划；或多个分别验收的阶段存在先后依赖。产品和维护都可能需要计划；单一明确任务可直接开发。
Required context
用户目标、已确认范围/验收、现状入口、相关需求/设计、当前计划、真实代码与验证命令。
Workflow
- 按实际规模选择更新现有短任务或 Phase；用户点名 Phase 时落实，不用口头计划代替文件。
- 范围对账：核对相关有效决定、非目标、延期和被替代记录。信息足够但缺形式变更记录时补写；只为真正未决选择提问。
- Phase 在实施前落盘目标、任务、前置 ID 和所需成果、验收及风险理由；小型产品变更只需短任务和需求更新。
- 索引维护活跃/下一步及历史导航；更新承接关系，不重抄全部历史。
- 先判断任务今天是否适用，再判断当时是否完成。按有效撤销/替代决定移出失效任务；部分替代只关闭相关部分，旧未测试记录不自动成为下一步。必要时使用 project-knowledge 对账。
Output
短任务或 docs/DEV-PLAN.md 与相关 Phase 明细；范围对账、depends_on、必要的 supersedes、验收和分别记录的状态。
Stop or escalate
只有影响方向/范围/验收的未决项阻塞其依赖阶段；不把缺模板变成用户重新决定的理由。Phase 身份不决定 R2；按具体后果评级。
References
编写计划时读 stage-contract.md；文档与状态细则读共同契约相关章节。
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.
- 7d ago Changed · +1 lines · -24 tokens per session 7f75ee0f4319
- 1mo ago Changed · -17 lines · -5 tokens per session ef2c390b5f29
- 1mo ago First seen · 55 lines · 62 tokens per session scan A d664f090be1e
dev-planner is a skill published in the GitHub repository arctan303/creator.skill (19 stars, last pushed 7d ago), licensed MIT. It adds 33 tokens to every session and 477 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
issue-triage
Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).
multi-agent
A process for coordinating multiple coding agents by splitting work among scouts, workers, reviewers, and repair agents. Each agent has a defined role and task.
tencent-meeting-mcp
A Tencent Meeting assistant for scheduling meetings and working with participants, recordings, transcripts, and AI-generated meeting notes.
flow-next-flow
Use first in a Flow-Next repo for a spec id, change, bug, issue, slow code or metric, cleanup, design fork, dump to explain, repeated mistake, prompt change, what could break, what next. No quick asks.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
flow-next-plan
Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).