A backlog-planning skill that drafts a new task with a description, testable acceptance criteria, priority, and estimate before saving it.

Use it to add features or other work to the correct phase backlog and define what must be true for the task to be accepted.

It turns a broad feature request into a specific piece of work that can be checked when finished, while requiring confirmation first.

add-task — Skill for Claude Code by natthasath

Install

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.

Any agent

npx skills add natthasath/natthasath-marketplace --skill add-task

Clone the repo

git clone --depth 1 https://github.com/natthasath/natthasath-marketplace

Made for: Claude Code.

Or install projects, the plugin that ships this one along with the rest of its 15 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/add-task/github.svg)](https://agentmods.dev/skills/natthasath/natthasath-marketplace/add-task)

Your own site

<a href="https://agentmods.dev/skills/natthasath/natthasath-marketplace/add-task"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/add-task/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/natthasath/natthasath-marketplace/add-task"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/add-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 711 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00057	$0.00711
Opus 5	$0.00028	$0.00356
Sonnet 5	$0.00011	$0.00142
Haiku 4.5	$0.00006	$0.00071

Measured 10d ago against content hash 89ab6e8c3ef5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade B, and why

add-task scanned grade B with 1 finding 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 10d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

!`cat .claude/config/task-format.md 2>/dev/null`

plugins/projects/skills/add-task/SKILL.md · 79 lines

What it actually says

!cat .claude/config/task-format.md 2>/dev/null

เพิ่ม task ใหม่เข้า backlog: $ARGUMENTS

เรียบเรียงความต้องการ — วิเคราะห์ $ARGUMENTS แล้วร่าง task draft:
- ชื่อ task: กระชับ ≤ 60 ตัวอักษร บอก action + object ชัดเจน
- Description: ขยายความว่าต้องทำอะไร ทำไม และขอบเขตคืออะไร (2-4 ประโยค)
- Acceptance Criteria: 2-4 ข้อที่ตรวจสอบได้จริง (testable, specific)
- Priority: ประเมินจาก context (High / Medium / Low)
- Estimate: ประเมินชั่วโมงหรือ story points ที่ต้องใช้
แสดง draft ให้ confirm ในรูปแบบนี้:
```
📋 Task Draft

ชื่อ: <ชื่อ task>
Priority: <High/Medium/Low>
Estimate: <X> hour(s)

Description:
<description>

Acceptance Criteria:
- [ ] <criteria 1>
- [ ] <criteria 2>
...
```
แล้วถามว่า "ต้องการแก้ไขส่วนไหนไหม หรือ OK ให้เพิ่มลง backlog เลย?"
รอ confirm — ถ้าผู้ใช้บอก OK หรือ ยืนยัน ถึงไปขั้นต่อไป ถ้าต้องการแก้ให้แก้แล้วแสดง draft ใหม่
อ่าน format จาก output ของ !cat ด้านบน (บรรทัด format:) แล้วกำหนด ID ตามนี้:

format: phase → อ่าน phase: จาก .claude/config/current-phase.md แล้วเปิด context/tasks/backlog/phase_<N>_*.md หา ID สูงสุด generate ต่อ
- ตัวอย่าง: phase 1, ID ล่าสุด TSK-1-008 → ID ใหม่ TSK-1-009
format: global → สแกน backlog ทุกไฟล์ใน context/tasks/backlog/ หา ID ตัวเลขสูงสุดทั่วทั้งโปรเจค
- ตัวอย่าง: ถ้ามี TSK-012 อยู่แล้ว → ID ใหม่ TSK-013

เพิ่ม entry ต่อท้าย backlog file ของ phase ปัจจุบัน:

## <ID ใหม่> — <ชื่อ task ที่ confirm แล้ว>

**Priority:** <priority>
**Estimate:** <X> hour(s)
**Status:** Backlog

**Description:**
<description>

**Acceptance Criteria:**
- [ ] <criteria 1>
- [ ] <criteria 2>

---

แจ้ง task ID ที่ได้ แล้วปิดท้ายด้วยบรรทัดนี้เสมอ:

─────────────────────────────
ถัดไป → /start-task <ID>
─────────────────────────────

Changes

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.

10d ago First seen · 79 lines · 57 tokens per session scan B 89ab6e8c3ef5

Subscribe to this mod's changes

add-task is a skill published in the GitHub repository natthasath/natthasath-marketplace (1 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 711 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Project management claude claude-marketpla claude-plugin claude-skills

customer-success-management

Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…

cbrock84/headcount · 85 tokens

chief-information-officer

The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost…

cbrock84/headcount · 79 tokens

service-desk

Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…

cbrock84/headcount · 73 tokens

chief-operating-officer

Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…

cbrock84/headcount · 94 tokens

head-of-pmo

The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. Use this to stand up or reform a PMO, decide what it should and should not control, judge whether it is adding value or overhead, or work out why teams route around it.

cbrock84/headcount · 72 tokens

chief-product-officer

Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market…

cbrock84/headcount · 96 tokens

add-task