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/uucz/moyuWrote 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/uucz/moyu/marketplace)<a href="https://agentmods.dev/plugins/uucz/moyu/marketplace"><img src="https://agentmods.dev/badge/plugins/uucz/moyu/marketplace/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/uucz/moyu/marketplace"><img src="https://agentmods.dev/badge/plugins/uucz/moyu/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
moyu marketplace 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 2mo 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": "moyu",
"display_name": "ζΈι±Ό (Moyu)",
"tagline": "Teach your AI agent when to stop over-engineering",
"category": "Productivity",
"tags": [
"anti-over-engineering",
"minimalism",
"code-quality",
"scope-control"
],
"platforms": [
"claude-code",
"cursor",
"codex-cli",
"vscode",
"windsurf",
"cline",
"kiro",
"codebuddy",
"antigravity",
"opencode",
"aider",
"continue"
],
"languages": ["zh-CN", "en", "ja", "ko", "fr"]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen Β· 28 lines scan A f205290bd37b
moyu marketplace is a plugin published in the GitHub repository uucz/moyu (294 stars, last pushed 3mo 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-30.
moyu marketplace compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| moyu marketplaceuucz/moyu | Plugin | 294 | 3mo ago | MIT | A | β | Claude Code |
| before-you-buildwshobson/agents | Plugin | 42k | yesterday | MIT | A | β | Claude Code |
| mc-agent-toolkitmonte-carlo-data/mc-agent-toolkit | Plugin | 93 | 2d ago | Apache-2.0 | A | β | Cursor |
| mosaic-bridgeMosaicXR-AI/mosaic-bridge | Plugin | 11 | 3d ago | none | A | β | Claude Code |
| kagekage-core/Kage | Plugin | 41 | 2mo ago | GPL-3.0 | A | β | Claude Code |
| collateMidnightDarling/collate | Plugin | 8 | 5mo ago | Apache-2.0 | A | β | Claude Code |
| humanizerblader/humanizer | Plugin | 65k | 10d ago | MIT | A | β | Claude Code |