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 implementgit 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/implement)<a href="https://agentmods.dev/skills/natthasath/natthasath-marketplace/implement"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/implement/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/implement"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/implement.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.00593 |
| Opus 5 | $0.00026 | $0.00296 |
| Sonnet 5 | $0.00011 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade B, and why
implement 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 9d 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/tech-stack.md .claude/config/current-phase.md context/tasks/in_progress/current_sprint.md 2>/dev/null` What it actually says
!cat .claude/config/tech-stack.md .claude/config/current-phase.md context/tasks/in_progress/current_sprint.md 2>/dev/null
Implement task: $ARGUMENTS
-
อ่าน
phase:จาก config ด้านบน แล้วเปิดcontext/tasks/backlog/phase_<N>_*.mdเพื่อหา task$ARGUMENTS- ถ้าหา task ไม่เจอใน phase ปัจจุบัน ให้สแกน backlog ทุก phase
- ถ้าไม่เจอเลย ให้แจ้ง error และหยุด
-
ตรวจสอบว่า task นี้อยู่ใน
current_sprint.mdแล้ว (status: 🔄 In Progress)- ถ้ายังไม่อยู่ ให้แจ้ง "รัน /start-task $ARGUMENTS ก่อน" แล้วหยุด
-
Implement ตาม Description และ Acceptance Criteria โดยยึดหลัก:
- Architecture ตาม
CLAUDE.md - Coding standards ตาม
.claude/rules/coding-standards.md - เขียน unit tests ควบคู่กับ implementation
- Architecture ตาม
-
หลัง implement เสร็จ รันตรวจสอบตามลำดับ (ใช้ commands จาก tech-stack.md ด้านบน):
- typecheck command
- lint command
- test command
ถ้ามี error — แก้ให้ผ่านก่อนทุกกรณี อย่ารายงานว่าเสร็จจนกว่าทั้ง 3 คำสั่งจะ pass
-
อัปเดต Acceptance Criteria ใน backlog file:
- เปลี่ยน
- [ ]เป็น- [x]สำหรับทุกข้อที่ implement เสร็จแล้ว - ข้อที่ยังไม่เสร็จให้คง
- [ ]ไว้
- เปลี่ยน
-
สรุปผล:
- ✅ Acceptance Criteria แต่ละข้อ — pass หรือ pending
- ⚠️ สิ่งที่ยังค้างหรือต้องทำต่อ (ถ้ามี)
ถ้า criteria ครบทุกข้อ ปิดท้ายด้วย:
───────────────────────────────────── ถัดไป → /ship $ARGUMENTS ─────────────────────────────────────ถ้ายังมี criteria ค้าง ปิดท้ายด้วย:
───────────────────────────────────── ถัดไป → /implement $ARGUMENTS (criteria ยังไม่ครบ) ─────────────────────────────────────
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.
- 9d ago First seen · 56 lines · 53 tokens per session scan B c4d698b1a92c
implement is a skill published in the GitHub repository natthasath/natthasath-marketplace (1 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 593 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
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-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…