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-phasegit 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-phase)<a href="https://agentmods.dev/skills/natthasath/natthasath-marketplace/done-phase"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/done-phase/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-phase"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/done-phase.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.00073 | $0.00782 |
| Opus 5 | $0.00036 | $0.00391 |
| Sonnet 5 | $0.00015 | $0.00156 |
| Haiku 4.5 | $0.00007 | $0.00078 |
Grade B, and why
done-phase 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 11d 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 && echo "---" && cat context/plans/PLAN.md 2>/dev/null` How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
!cat .claude/config/current-phase.md 2>/dev/null && echo "---" && cat context/plans/PLAN.md 2>/dev/null
Mark phase ปัจจุบันว่าเสร็จแล้ว และเริ่ม phase ถัดไป
Input: $ARGUMENTS (ถ้าไม่มี ใช้ phase จาก config ด้านบน)
ขั้นที่ 1 — ตรวจสอบ phase ที่จะ done
อ่าน phase: จาก config ด้านบน (หรือใช้ $ARGUMENTS ถ้ามี)
- ถ้า phase นั้น status ไม่ใช่ 🔄 In Progress ใน PLAN.md — แจ้ง "Phase ยังไม่ได้เริ่มทำงาน" แล้วหยุด
ขั้นที่ 2 — ตรวจสอบ tasks ค้างใน sprint
อ่าน context/tasks/in_progress/current_sprint.md
- ถ้ายังมี entries ที่มี
**Status:** 🔄 In Progressอยู่ใน current_sprint.md — แจ้งรายการและถามว่า "ยังมี tasks ค้างอยู่ ต้องการดำเนินการต่อไหม? (y/n)" - ถ้า n — หยุด
- ถ้า y — ดำเนินการต่อ
ขั้นที่ 3 — อัปเดต PLAN.md
แก้ไข context/plans/PLAN.md:
- เปลี่ยน row ของ phase ปัจจุบัน:
🔲 Not Startedหรือ🔄 In Progress→✅ Done - ถ้ามี phase ถัดไป (N+1) อยู่ใน PLAN.md: เปลี่ยน
🔲 Not Started→🔄 In Progress
ขั้นที่ 4 — อัปเดต phase plan file
ก่อนแก้ไข: หา slug จริงของ phase ด้วย Bash glob
ls context/plans/phase_<N>_*.md 2>/dev/null | head -1
ใช้ชื่อไฟล์ที่ได้จาก glob (เช่น context/plans/phase_1_foundation.md) ในขั้นตอนถัดไป
แก้ไข context/plans/phase_<N>_<slug>.md (ชื่อไฟล์จาก glob ด้านบน):
- เปลี่ยน
**Status:** 🔄 In Progress→**Status:** ✅ Done - เพิ่มบรรทัด
**Completed:** YYYY-MM-DD(วันนี้)
ขั้นที่ 5 — อัปเดต current-phase config
เขียน .claude/config/current-phase.md ให้ phase: เป็นเลข phase ถัดไป (N+1)
- ถ้าไม่มี phase ถัดไปใน PLAN.md — ให้
phase:คงค่าเดิมและแจ้ง "นี่คือ phase สุดท้าย 🎉"
ขั้นที่ 6 — สรุปผล
✅ Phase <N> — <ชื่อ> เสร็จสมบูรณ์
ไฟล์ที่อัปเดต:
✅ context/plans/PLAN.md
✅ context/plans/phase_<N>_<slug>.md
✅ .claude/config/current-phase.md (→ phase <N+1>)
แล้วปิดท้ายด้วย:
─────────────────────────────────────────────────
ถัดไป → /status (ดูภาพรวมโปรเจค)
/add-task <desc> (เพิ่ม tasks ใน phase ถัดไป)
─────────────────────────────────────────────────
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.
- 11d ago First seen · 72 lines · 73 tokens per session scan B 74ca8d62f209
done-phase is a skill published in the GitHub repository natthasath/natthasath-marketplace (1 stars, last pushed 3d ago), licensed MIT. It adds 73 tokens to every session and 782 once invoked, about $0.0004 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
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…
chief-technology-officer
Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeoffs, platform and tooling decisions, or when a technical choice has business…
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-content-officer
Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit…