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.
git 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/plugins/natthasath/natthasath-marketplace/projects)<a href="https://agentmods.dev/plugins/natthasath/natthasath-marketplace/projects"><img src="https://agentmods.dev/badge/plugins/natthasath/natthasath-marketplace/projects/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/plugins/natthasath/natthasath-marketplace/projects"><img src="https://agentmods.dev/badge/plugins/natthasath/natthasath-marketplace/projects.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
projects 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.
What it actually says
{
"name": "projects",
"version": "0.3.4",
"description": "Plugin สำหรับ setup และจัดการ development project — scaffold โครงสร้าง context/, rules, config พร้อม skills ครบ workflow ตั้งแต่ setup จนถึง ship",
"author": {
"name": "natthasath"
},
"keywords": [
"project",
"setup",
"workflow",
"tasks",
"phases",
"checkpoint",
"implement",
"ship",
"debug",
"status"
]
}What it installs
The manifest is a name and a version. 15 skills travel with it, and installing the plugin installs all of them — 861 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill setup A 67 tokens
- Skill add-phase A 51 tokens
- Skill list-phase A 58 tokens
- Skill set-stack A 71 tokens
- Skill status A 54 tokens
- Skill checkpoint A 49 tokens
- Skill today A 61 tokens
- Skill add-task B 57 tokens
- Skill done-phase B 73 tokens
- Skill implement B 53 tokens
- Skill done-task B 53 tokens
- Skill list-task B 57 tokens
- Skill ship B 48 tokens
- Skill start-task B 54 tokens
- Skill debug B 55 tokens
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 · -17 lines b0654973c920
- 1mo ago First seen · 37 lines scan A 1dd732c53fac
projects is a plugin published in the GitHub repository natthasath/natthasath-marketplace (1 stars, last pushed 14d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
pmo
Enterprise program management office: portfolio governance, program and project delivery, dependencies and delivery risk, benefits realization, and adoption.
operations
Program management, process design, vendor and supplier management, and operational delivery.
people
Org design, hiring and interviewing, compensation and leveling, and workforce planning.
revenue
Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.
agile-ledger
Plain-Markdown Scrum/Agile product management for Claude Code — backlog, sprints, board, velocity, releases, and GitHub traceability from slash commands. The ledger lives in its own repo, one folder per project, so code repos stay clean.
situate
Gain situational awareness before modifying code. Scans branches, PRs, tickets, and project conventions to orient the agent and verify the work required.