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 add-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/add-phase)<a href="https://agentmods.dev/skills/natthasath/natthasath-marketplace/add-phase"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/add-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/add-phase"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/add-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.00051 | $0.01007 |
| Opus 5 | $0.00026 | $0.00504 |
| Sonnet 5 | $0.00010 | $0.00201 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
add-phase 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
!cat context/plans/PLAN.md 2>/dev/null
เพิ่ม phase ใหม่เข้าโปรเจค: $ARGUMENTS
Format: /add-phase <ชื่อ phase> [target date]
ตัวอย่าง: /add-phase "API Integration" 2026-09-01
ขั้นที่ 1 — วิเคราะห์ argument
แยก $ARGUMENTS ออกเป็น:
- ชื่อ phase — ทุกอย่างก่อน date pattern
YYYY-MM-DD(ถ้ามี) - target date — ถ้ามี date pattern ใน argument ให้ใช้, ถ้าไม่มีให้ใส่
TBD - slug — lowercase, replace space ด้วย
-(เช่น "API Integration" →api-integration)
ขั้นที่ 2 — หา phase number ถัดไป
อ่าน Status Overview table จาก PLAN.md ด้านบน หา phase number สูงสุดแล้วบวก 1
- ถ้าไม่มี phase เลย ให้เริ่มที่ phase
1
ขั้นที่ 3 — Draft และขอ confirm
แสดง preview ก่อน:
📋 Phase Draft
Phase: <N> — <ชื่อ>
Target: <date หรือ TBD>
Files ที่จะสร้าง:
· context/plans/PLAN.md (เพิ่ม row)
· context/plans/phase_<N>_<slug>.md (สร้างใหม่)
· context/tasks/backlog/phase_<N>_backlog.md (สร้างใหม่)
· context/tasks/completed/archive.md (เพิ่ม section)
ถามว่า "ต้องการแก้ไขอะไรไหม หรือ OK ให้สร้างเลย?" รอ confirm ก่อนทำขั้นต่อไป
ขั้นที่ 4 — อัปเดต PLAN.md
เพิ่ม row ต่อท้าย Status Overview table:
| <N> | <ชื่อ> | 🔲 Not Started | <date> |
เพิ่ม link ต่อท้าย Phase Files section:
- [Phase <N>: <ชื่อ>](phase_<N>_<slug>.md)
ขั้นที่ 5 — สร้าง phase plan file
สร้าง context/plans/phase_<N>_<slug>.md:
# Phase <N>: <ชื่อ>
**Status:** 🔲 Not Started
**Target:** <date หรือ TBD>
**Depends on:** Phase <N-1> complete
**Goal:** <สรุปสั้นๆ จากชื่อ phase — แก้ไขได้ภายหลัง>
## Objectives
_(เพิ่ม objectives เมื่อวางแผน)_
## Deliverables
_(เพิ่ม deliverables เมื่อวางแผน)_
## Acceptance Criteria
- [ ] _(เพิ่ม criteria เมื่อวางแผน)_
ขั้นที่ 6 — สร้าง backlog file
สร้าง context/tasks/backlog/phase_<N>_backlog.md:
# Phase <N> Backlog — <ชื่อ>
_(เพิ่ม tasks ด้วย /add-task)_
ขั้นที่ 7 — อัปเดต current-phase config (เฉพาะกรณีแรก)
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 · 137 lines · 51 tokens per session scan A 8a2198b68d0a
add-phase is a skill published in the GitHub repository natthasath/natthasath-marketplace (1 stars, last pushed 3d ago), licensed MIT. It adds 51 tokens to every session and 1,007 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
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…