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/arctan303/creator.skill/dev-plannernpx skills add arctan303/creator.skill --skill dev-plannergit clone --depth 1 https://github.com/arctan303/creator.skillWhat 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.00062 | $0.00830 |
| Opus 5 | $0.00031 | $0.00415 |
| Sonnet 5 | $0.00012 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
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 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
开发计划技能 (dev-planner)
Purpose
把已确认的产品契约拆成另一个开发者可直接执行、验证和审查的 Phase 计划。
Trigger
- 0→1 产品已有可验收 Product Spec，需要完整开发计划。
- 产品变更已有变更记录，需要增量 Phase。
- 当前工作不是普通 Bug、内部重构、文档或其他维护任务。
Required context
- 可验收的
Product-Spec.md和相关变更 ID。 Design-Brief.md或设计产物（如果相关）。- 现有仓库、脚本、测试、CI、技术栈和平台事实。
- 依赖、非目标、迁移与发布约束。
Workflow
- 扫描仓库事实，拒绝凭空假设技术栈或文件结构。
- 范围对账（切分 Phase 前必做）：扫描 Product Spec 与既有计划中与本次范围相关的非目标、延期或“先不管”声明，逐条三分——
- 仍成立 → 保持；
- 被本次承接 → 修订并标记“由 Phase N 承接，本声明作废”，把“更新 Spec 受影响章节”排进该 Phase 任务；
- 承接但无变更记录 → 暂停，返回
product-spec-builder记录变更，不直接追加。
- 按可运行、可演示、可审查的能力切分 Phase；索引与明细分离。
- 每个 Phase 映射
REQ-*、AC-*或产品变更 ID。 - 索引
docs/DEV-PLAN.md维护状态总览与 Phase 清单；明细写入docs/dev-plan/phase-NN.md，写明预期文件/产物、依赖、验证命令和交付证据。 - 标记 R2 审查要求；产品变更只更新受影响范围，不改写已完成 Phase 的实现细节。
Output
docs/DEV-PLAN.md索引：状态总览、规则边界、当前 Phase、每行 =能力 + 状态 + REQ-AC 映射 + 验证命令 + 明细链接 + 完成证据摘要。docs/dev-plan/phase-NN.md明细：目标 / 范围与非范围 / 依赖 / 任务与预期文件 / REQ-AC 映射 / 验证命令与证据 / 审查要求 + 完成证据追加区。- 范围对账结果：被承接 / 作废 / 保留的声明清单及对应 Phase。
- 0→1 的完整 Phase，或产品变更的增量 Phase；依赖、非目标和审查门禁。
Stop or escalate
- 当前任务实际属于维护路线：转交维护执行，不生成产品 Phase。
- Product Spec 或变更记录不可验收：返回
product-spec-builder。 - 承接既有非目标/延期声明但无变更记录：返回
product-spec-builder，不直接追加 Phase。 - 依赖、影响范围或用户决策不清：停止并指出最小阻塞。
- Phase 无法独立运行、验证或审查：重新切分后再输出。
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.
- 2d 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 (20 stars, last pushed 28d ago), licensed MIT. It adds 62 tokens to every session and 830 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-08-30.
Other skills, from other repositories
agent-team
Build low-context multi-agent teams with durable handoff, independent review, and user gates. Use when a project needs separate management, execution, and review roles.
agent-team
Build low-context multi-agent teams with durable handoff, independent review, and user gates. Use when a project needs separate management, execution, and review roles.
aip-tracker
Track Airflow Improvement Proposal (AIP) implementation progress by comparing Confluence specs against codebase evidence. Use when asked to assess, report on, or compare AIP status.
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).
meeting-note-summarizer
Turn meeting notes or transcripts into factual summaries, decisions, questions, and action items. Use when a user wants a concise recap or needs explicit owners and deadlines extracted without filling in missing details.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…