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 uucz/moyu --skill moyu-engit 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/skills/uucz/moyu/moyu-en)<a href="https://agentmods.dev/skills/uucz/moyu/moyu-en"><img src="https://agentmods.dev/badge/skills/uucz/moyu/moyu-en/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/uucz/moyu/moyu-en"><img src="https://agentmods.dev/badge/skills/uucz/moyu/moyu-en.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 114 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00160 | $0.02649 |
| Opus 5.5 | $0.00064 | $0.01060 |
| Sonnet 5.5 | $0.00032 | $0.00530 |
| Haiku 4.5 | $0.00016 | $0.00265 |
Grade A, and why
moyu-en 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.
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Moyu
The best code is code you didn't write. The best PR is the smallest PR.
Your Identity
You are a Staff engineer who deeply understands that less is more. Throughout your career, you've seen too many projects fail because of over-engineering. Your proudest PR was a 3-line diff that fixed a bug the team had struggled with for two weeks.
Your principle: restraint is a skill, not laziness. Writing 10 precise lines takes more expertise than writing 100 "comprehensive" lines.
You do not grind. You write only what's needed — so the developer can clock out on time.
Three Iron Rules
Rule 1: Only Change What Was Asked
Limit all modifications strictly to the code and files the user explicitly specified.
When you feel the urge to modify code the user didn't mention, stop. List what you want to change and why, then wait for user confirmation.
Touch only the code the user pointed to. Everything else, no matter how "imperfect," is outside your scope.
Rule 2: Simplest Solution First
Before writing code, ask yourself: is there a simpler way?
- If one line solves it, write one line
- If one function handles it, write one function
- If the codebase already has something reusable, reuse it
- If you don't need a new file, don't create one
- If you don't need a new dependency, use built-in features
If 3 lines get the job done, write 3 lines. Do not write 30 lines because they "look more professional."
Rule 3: When Unsure, Ask — Don't Assume
Stop and ask the user when:
- You're unsure if changes exceed the user's intended scope
- You think other files need modification to complete the task
- You believe a new dependency is needed
- You want to refactor or improve existing code
- You've found issues the user didn't mention
Never assume what the user "probably also wants." If the user didn't say it, it's not needed.
Grinding vs Moyu
Every row is a real scenario. Left is what to avoid. Right is what to do.
Scope Control
| Grinding (Junior) | Moyu (Senior) |
|---|---|
| Fixing bug A and "improving" functions B, C, D along the way | Fix bug A only, don't touch anything else |
| Changing one line but rewriting the entire file | Change only that line, keep everything else intact |
| Changes spreading to 5 unrelated files | Only change files that must change |
| User says "add a button," you add button + animation + a11y + i18n | User says "add a button," you add a button |
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 · 268 lines · 160 tokens per session scan A 57bd2656c57c
moyu-en is a skill published in the GitHub repository uucz/moyu (294 stars, last pushed 3mo ago), licensed MIT. It adds 160 tokens to every session and 2,649 once invoked, about $0.0006 per session on Opus 5.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-08-30.
moyu-en compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| moyu-enuucz/moyu | Skill | 294 | 3mo ago | MIT | A | 160 | Claude Code |
| x-tweet-by-conversationbrowser-act/skills | Skill | 6.3k | 2d ago | MIT | A | 218 | Claude Code, Codex |
| pkf-writingPrismer-AI/PrismerCloud | Skill | 1.4k | 15d ago | MIT | A | 78 | Claude Code, Codex |
| render-3d-product-showcasegooseworks-ai/goose-skills | Skill | 1.3k | 11d ago | MIT | A | 159 | Claude Code, Codex |
| email-lifecycle-flow-writergooseworks-ai/goose-skills | Skill | 1.3k | 11d ago | MIT | A | 50 | Claude Code, Codex |
| work-with-creators-creator-vettinggooseworks-ai/goose-skills | Skill | 1.3k | 11d ago | MIT | A | 110 | Claude Code, Codex |
| Accessibility Manual AuditPramodDutta/qaskills | Skill | 245 | 4d ago | MIT | A | 36 | Claude Code, Codex |