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 todaygit 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/today)<a href="https://agentmods.dev/skills/natthasath/natthasath-marketplace/today"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/today/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/today"><img src="https://agentmods.dev/badge/skills/natthasath/natthasath-marketplace/today.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.00061 | $0.00280 |
| Opus 5 | $0.00030 | $0.00140 |
| Sonnet 5 | $0.00012 | $0.00056 |
| Haiku 4.5 | $0.00006 | $0.00028 |
Grade A, and why
today 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 3d 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.
What it actually says
สรุปงานที่ทำวันนี้
-
รัน
git log --oneline --since="midnight" --author="$(git config user.name)"เพื่อดู commits วันนี้ -
อ่าน
context/tasks/in_progress/current_sprint.md— มีงานที่ยังค้างอยู่ไหม -
อ่าน
context/tasks/completed/archive.md— กรอง entries ที่มี**Completed:** <วันนี้>เพื่อดู tasks ที่เสร็จวันนี้ -
สรุปใน 3-5 bullet points:
- ✅ ทำเสร็จแล้ว: (tasks จาก archive + commits)
- 🔄 กำลังทำ: (tasks ใน current_sprint)
- 📋 รอทำต่อพรุ่งนี้: (tasks ที่ยังค้างใน current_sprint)
แล้วปิดท้ายด้วย:
───────────────────────────────────── ถัดไป → /status (ภาพรวมโปรเจค) ─────────────────────────────────────
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.
- 3d ago First seen · 29 lines · 61 tokens per session scan A 8c4a4d7e639b
today is a skill published in the GitHub repository natthasath/natthasath-marketplace (1 stars, last pushed 4d ago), licensed MIT. It adds 61 tokens to every session and 280 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-09-09.
Other skills, from other repositories
worktrees
Use when fanning several tickets into parallel branches and git worktrees, with related tickets grouped together.
what
Use when the user asks what is going on and needs a five-line summary of the session, branch, pull request, and ticket.
team-workspace
Use to set up or work with a SHARED, git-backed team workspace for artifacts a team co-owns — team charters, strategy docs, decision records — kept strictly separate from your private reflections, which never leave your machine. Trigger phrases include "share our team charter with the team", "set up a shared…
worktree
Use when taking one ticket or a related ticket group into its own branch and git worktree for implementation.
situational-awareness
Use when you came back to a branch/PR: the work you were in the middle of, where it left off, repo state, and what reviewers ask or the PR waits on.
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…