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 list-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/list-task)<a href="https://agentmods.dev/skills/natthasath/natthasath-marketplace/list-task"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/list-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/list-task"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/list-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.00057 | $0.00595 |
| Opus 5.5 | $0.00023 | $0.00238 |
| Sonnet 5.5 | $0.00011 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade B, and why
list-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 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.
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
Task List Viewer
แสดง tasks ที่จะทำต่อไปทั้งหมดในโปรเจค
Filter (optional): $ARGUMENTS — กรองตาม priority (high/medium/low) หรือ keyword ใน title
Core Rules (Non-negotiable)
- ข้าม section ที่ไม่มี tasks — ไม่แสดง section เปล่า
- เรียง Backlog ตาม Priority เสมอ: High → Medium → Low
- ข้าม tasks ที่มี
Status: ✅ Doneเสมอ ไม่ว่าจะอยู่ใน section ไหน - Feature Requests แสดงเฉพาะที่ยังไม่ assign phase
Workflow
1. อ่านข้อมูล
อ่าน phase: จาก config ด้านบน แล้วอ่านไฟล์เหล่านี้พร้อมกัน:
context/tasks/in_progress/current_sprint.md→ tasks ที่กำลังทำอยู่context/tasks/backlog/phase_<N>_*.md→ tasks ที่รอทำ (phase ปัจจุบัน)context/tasks/backlog/feature_requests.md→ feature requests ที่ยังไม่ได้ assign (ถ้ามี)
2. กรองผล (ถ้ามี)
ถ้ามี $ARGUMENTS ให้ filter เฉพาะ tasks ที่ตรงกับ keyword หรือ priority นั้น
3. แสดงผล
แสดงผลในรูปแบบนี้ (ตาม Core Rules ด้านบนเรื่องลำดับและการข้าม section):
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TASK LIST
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🔄 IN PROGRESS
[TSK-X-XXX] ชื่อ task — X hour(s)
📋 BACKLOG — High Priority
[TSK-X-XXX] ชื่อ task — X hour(s)
📋 BACKLOG — Medium Priority
[TSK-X-XXX] ชื่อ task — X hour(s)
📋 BACKLOG — Low Priority
[TSK-X-XXX] ชื่อ task — X hour(s)
💡 FEATURE REQUESTS (unassigned)
[FR-XXX] ชื่อ feature — Priority: Low
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
รวม: X tasks (Y in progress, Z รอทำ)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
─────────────────────────────────────
ถัดไป → /start-task [TSK ที่ควรทำต่อไป]
─────────────────────────────────────
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 · +8 lines d1b91d19cdb4
- 1mo ago First seen · 61 lines · 57 tokens per session scan B 2364f76e98fd
list-task is a skill published in the GitHub repository natthasath/natthasath-marketplace (1 stars, last pushed 14d ago), licensed MIT. It adds 57 tokens to every session and 595 once invoked, about $0.0002 per session on Opus 5.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-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…