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 natthasath/natthasath-marketplace --skill done-taskgit clone --depth 1 https://github.com/natthasath/natthasath-marketplaceWrote 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/natthasath/natthasath-marketplace/done-task)<a href="https://agentmods.dev/skills/natthasath/natthasath-marketplace/done-task"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/done-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.
<a href="https://agentmods.dev/skills/natthasath/natthasath-marketplace/done-task"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/done-task.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.00053 | $0.00485 |
| Opus 5 | $0.00026 | $0.00243 |
| Sonnet 5 | $0.00011 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade B, and why
done-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/current-phase.md 2>/dev/null` What it actually says
!cat .claude/config/current-phase.md 2>/dev/null
Mark task เสร็จแล้ว: $ARGUMENTS
-
อ่าน
context/tasks/in_progress/current_sprint.md- ค้นหา entry ของ task
$ARGUMENTS - ถ้าไม่เจอ — แจ้งเตือน "Task $ARGUMENTS ไม่อยู่ใน current_sprint.md ลองรัน /start-task $ARGUMENTS ก่อน" แล้วหยุด
- ค้นหา entry ของ task
-
อ่าน
phase:จาก config ด้านบน แล้วเปิดcontext/tasks/backlog/phase_<N>_*.md- ถ้าไม่พบ task ใน backlog ของ phase ปัจจุบัน ให้สแกน backlog ทุก phase
- เปลี่ยน
**Status:** Backlogหรือ**Status:** 🔄 In Progressเป็น**Status:** ✅ Done (YYYY-MM-DD)โดยใช้วันที่วันนี้
-
แก้
context/tasks/in_progress/current_sprint.md- ลบ entry ทั้งหมดของ task
$ARGUMENTSออก (ตั้งแต่ heading ถึง---ถัดไป) - เพิ่ม row ใน Sprint Log:
| YYYY-MM-DD | $ARGUMENTS | Completed | - |
- ลบ entry ทั้งหมดของ task
-
อ่าน
context/tasks/completed/archive.mdแล้ว append task นี้:### $ARGUMENTS — <ชื่อ task จาก backlog> **Completed:** YYYY-MM-DD **Phase:** <phase number> **Notes:** - -
รัน
git log --oneline -5เพื่อแสดง commits ที่เกี่ยวข้อง -
แจ้งสรุป:
- Task ที่ done
- ไฟล์ที่ถูก update (backlog, current_sprint, archive)
แล้วปิดท้ายด้วยบรรทัดนี้เสมอ:
───────────────────────────────────── ถัดไป → /status ─────────────────────────────────────
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 · 49 lines · 53 tokens per session scan B b44e271924e2
done-task is a skill published in the GitHub repository natthasath/natthasath-marketplace (1 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 485 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.
Other skills, from other repositories
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…
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…
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…
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…
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.
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…