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 setupgit 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/setup)<a href="https://agentmods.dev/skills/natthasath/natthasath-marketplace/setup"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/setup/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/setup"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/setup.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.00067 | $0.02778 |
| Opus 5.5 | $0.00027 | $0.01111 |
| Sonnet 5.5 | $0.00013 | $0.00556 |
| Haiku 4.5 | $0.00007 | $0.00278 |
Grade A, and why
setup 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 19d 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 — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Scaffold Setup
เตรียม project structure ใหม่สำหรับการพัฒนาด้วย Claude Code
Project name และ description: $ARGUMENTS
Core Rules (Non-negotiable)
- ต้องรอ confirm จากผู้ใช้ก่อนเริ่ม Execute (Step 2) เสมอ — ถ้าผู้ใช้ตอบ "no" ให้หยุดทันที ห้าม scaffold ไฟล์ใดๆ โดยไม่ได้รับอนุญาตก่อน
- สร้างไฟล์/โฟลเดอร์ให้ครบทุกรายการตามที่แสดงไว้ในแผน (Step 1) ห้ามข้ามรายการใดไปเฉยๆ
- ก่อนรายงานผลสำเร็จ (Step 3) ต้องตรวจสอบว่าแต่ละไฟล์/โฟลเดอร์ถูกสร้างขึ้นจริง ไม่ใช่แค่สมมติว่าสำเร็จ ถ้าไฟล์ไหนสร้างไม่สำเร็จ ให้แก้ไขหรือลองใหม่ก่อน ห้ามรายงาน ✓ ให้สิ่งที่ยังไม่เกิดขึ้นจริง
- git commit ทำเป็นลำดับสุดท้ายของ Step 2 เท่านั้น หลังสร้างไฟล์ทั้งหมดเสร็จสมบูรณ์แล้ว ไม่ commit ไฟล์ที่ยังสร้างไม่ครบ
Workflow
0. รับข้อมูล
ถ้า $ARGUMENTS ว่างเปล่า ให้ถามผู้ใช้ก่อน:
ชื่อโปรเจคของคุณคืออะไร? (เช่น "My API", "E-commerce Platform")
อธิบายสั้นๆ ว่าโปรเจคนี้ทำอะไร (1-2 ประโยค)
Parse $ARGUMENTS เป็น:
- PROJECT_NAME = token แรก (เช่น "my-api") หรือถามถ้าไม่มี
- DESCRIPTION = ส่วนที่เหลือ (quoted string หรือว่างก็ได้)
1. แสดงแผนและขอ confirm
แสดงรายการสิ่งที่จะสร้าง:
🗂️ setup: <PROJECT_NAME>
📄 สร้าง CLAUDE.md
📁 สร้าง .claude/config/
├── current-phase.md
├── task-format.md
└── tech-stack.md
📁 สร้าง .claude/rules/
├── git-conventions.md
├── coding-standards.md
├── error-handling.md
├── testing-rules.md
├── security-rules.md
└── performance-rules.md
📁 สร้าง context/
├── plans/PLAN.md
├── tasks/backlog/feature_requests.md
├── tasks/in_progress/current_sprint.md
├── tasks/completed/archive.md
├── memory/
└── docs/
ดำเนินการต่อไหม? (yes / no)
รอ confirm ก่อน — ถ้า no หยุดทันที
2. Execute (หลัง confirm เท่านั้น)
ทำตาม checklist นี้ทีละข้อจนครบ ห้ามข้ามข้อใดไป — แต่ละข้อคือไฟล์/โฟลเดอร์หนึ่งรายการจากแผนที่แสดงใน Step 1:
- 2a. CLAUDE.md
- 2b. .claude/config/current-phase.md
- 2c. .claude/config/task-format.md
- 2d. .claude/config/tech-stack.md
- 2e. .claude/rules/ (6 ไฟล์)
- 2f. context/plans/PLAN.md
- 2g. task files และ directories
- 2h. git initial commit (ทำหลังสุด หลังข้อ 2a-2g เสร็จครบเท่านั้น)
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 19d ago Changed · +13 lines ae64c42bc158
- 1mo ago First seen · 323 lines · 67 tokens per session scan A 91a1997ea365
setup is a skill published in the GitHub repository natthasath/natthasath-marketplace (1 stars, last pushed 14d ago), licensed MIT. It adds 67 tokens to every session and 2,778 once invoked, about $0.0003 per session on Opus 5.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-09-09.
Other skills, from other repositories
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…
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-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…
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-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…
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…