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/refactor)<a href="https://agentmods.dev/plugins/natthasath/natthasath-marketplace/refactor"><img src="https://agentmods.dev/badge/plugins/natthasath/natthasath-marketplace/refactor/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/refactor"><img src="https://agentmods.dev/badge/plugins/natthasath/natthasath-marketplace/refactor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
refactor 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 15d 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": "refactor",
"version": "0.6.2",
"description": "Plugin รวม Skills สำหรับ Refactor และปรับปรุงโครงสร้างไฟล์ ครอบคลุม Dockerfile, Docker Compose, Shell Script, README และโครงสร้าง command ของ CLI tool",
"author": {
"name": "natthasath"
},
"keywords": ["refactor", "dockerfile", "docker-compose", "shell-script", "readme", "markdown", "documentation", "emoji", "devops", "best-practices", "cli", "command-design", "help", "clap", "cobra", "click", "commander", "cross-platform"]
}
What it installs
The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 641 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 15d ago Changed 438b1d95d4a6
- 1mo ago First seen · 10 lines scan A 8ad0a38d0d8e
refactor is a plugin published in the GitHub repository natthasath/natthasath-marketplace (1 stars, last pushed 10d 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-09-09.
Other plugins, from other repositories
security
Threat modeling, security architecture review, incident response, vulnerability management, and access and identity. Reviewer-class: blocking findings are not overrulable by the department under review.
data-analytics
Data governance, warehouse and semantic modeling, business intelligence, and AI/ML governance.
executive
Direction, capital and attention allocation, cross-functional arbitration, strategy validation, and the method for structuring the organization itself.
revenue
Outbound, sales enablement, revenue operations, pricing and packaging, activation, retention, and referrals.
rudder-core
Cross-tool RudderStack domain knowledge: data catalog, data graphs, tracking plans, instrumentation planning, instrumentation debugging, and destination delivery debugging.
bugscribe
A single skill that files one already-identified bug as a new GitHub issue: verifies the defect against the source code, checks the backlog for duplicates, posts a short report pointing to a file and line, and pings the repository owner exactly once — it reports a known finding rather than searching for one.