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-doitnpx skills add KanoCifer/DevTaskMcp --skill devtask-doitgit 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.00051 | $0.00474 |
| Opus 5 | $0.00026 | $0.00237 |
| Sonnet 5 | $0.00010 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
devtask-doit 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-doit
流程
1. 拿到任务
get_task(slug, view="full")
按 ../references/task-contract.md 读取 Task Document 和 MCP 契约。
如果 kind == "spec"，先 list_children(parent_slug=slug) 拿子任务列表，挑下一个 subtask 执行；不要执行 spec 自身。
2. 读上下文
按 ## Context Pointers 章节里的 path:line 读代码/文档。不靠记忆。
3. 执行
按 ## Plan 章节实现。改动紧贴 spec，不顺手重构。
## Constraints 是硬性边界，违反之前先确认。
4. 验证 + 更新
逐条检查 ## Acceptance Criteria 的验收项；先检查再修，修完重跑直到全过。
需要固化决策时用 update_task(slug, detail=...)；普通执行日志不要写回 task。
当前任务全部通过 → update_task(slug, status="已完成")。
spec 的全部子任务完成后，可用 update_task(slugs=[...]) 批量标记；该接口仅更新状态为 已完成。
5. 交付
- 当前任务：slug + 状态
- 后续：未完成兄弟 → 建议下一个 slug；parent 完成 → "spec 已完成"
Rules
- Source of truth — 状态用
update_task；正文用update_task(slug, detail=...) - 不扩大范围 — 紧贴 spec 和 AC，不顺手重构
- 记录决策 — 关键变更写入
Decisions，不要写执行日志
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 · 46 lines · 51 tokens per session scan A 6b888ffbaa4d
devtask-doit is a skill published in the GitHub repository KanoCifer/DevTaskMcp (0 stars, last pushed 7d ago), licensed MIT. It adds 51 tokens to every session and 474 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.