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/kanocifer/devtaskmcp/devtask-setupnpx skills add KanoCifer/DevTaskMcp --skill devtask-setupgit clone --depth 1 https://github.com/KanoCifer/DevTaskMcpWhat 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.00056 | $0.00421 |
| Opus 5 | $0.00028 | $0.00211 |
| Sonnet 5 | $0.00011 | $0.00084 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
devtask-setup 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 yesterday.
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
devtask-setup
让一个新项目具备 devtask 工作流：检查环境，追加 CLAUDE.md 引导，交付初始化结果。
流程
1. 环境检查
- 检查
DEVTASK_API_KEY非空 - 调用
get_task("task-1")验证连通性（404 也算连通）
失败处理：
DEVTASK_API_KEY为空 → 提示从 kanocifer.chat 获取后终止- API 调用失败 → 报告错误并终止
2. 写 CLAUDE.md 引导
读取项目的 CLAUDE.md（或 ~/.claude/CLAUDE.md）。若已有 ## devtask 工作流，跳过；否则将 references/claude-md-template.md 调整项目 scope 示例后追加到末尾。
3. 交付
✅ devtask 初始化完成
环境: 已连通（API Key 有效）
引导: 已写入 CLAUDE.md（或已存在）
任务: <已创建 task-N / 暂未创建>
下一步: /devtask:devtask 创建第一个任务
Rules
- 幂等 — 重复运行不重复写入 CLAUDE.md，不重复创建 task
- 先检查再写 — 环境不通不写引导，避免无效配置
- 不覆盖用户内容 — 只追加 devtask 章节，不改动 CLAUDE.md 已有内容
What ships with it
1 file 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.
- yesterday First seen · 45 lines · 56 tokens per session scan A 40997e199189
devtask-setup is a skill published in the GitHub repository KanoCifer/DevTaskMcp (0 stars, last pushed 7d ago), licensed MIT. It adds 56 tokens to every session and 421 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-31.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.