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 meitu/meitu-skills --skill meitu-image-fixgit clone --depth 1 https://github.com/meitu/meitu-skillsWrote 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/meitu/meitu-skills/meitu-image-fix)<a href="https://agentmods.dev/skills/meitu/meitu-skills/meitu-image-fix"><img src="https://agentmods.dev/badge/skills/meitu/meitu-skills/meitu-image-fix/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/meitu/meitu-skills/meitu-image-fix"><img src="https://agentmods.dev/badge/skills/meitu/meitu-skills/meitu-image-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 8 findings, up to high
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 →
- high Privilege Escalation · line 5 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 7 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 13 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 15 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 19 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 65 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Tool Misuse · line 168 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Rogue Agent · line 33 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00113 | $0.04241 |
| Opus 5 | $0.00056 | $0.02121 |
| Sonnet 5 | $0.00023 | $0.00848 |
| Haiku 4.5 | $0.00011 | $0.00424 |
Grade A, and why
meitu-image-fix scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- curl Copies of this mod
2 near-identical copies found in the catalogue:
- meitu-product-view — 92% identical, 442 lines differ
- meitu-video-dance — 86% identical, 321 lines differ
How it starts
The opening of the file, as written. The whole thing — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meitu Image Fix
Overview
接收一张有问题的图片，自动诊断画质/人像/内容三类问题，规划最优修复管线，按顺序调用 meitu-cli 工具链完成修复。核心价值是诊断+串联——用户不需要知道该用哪个工具，只需要说"帮我修一下"。
Dependencies
- meitu-cli (>=2.0.6):
npm install -g meitu-cli@latest - 凭证: 首选 env
MEITU_OPENAPI_ACCESS_KEY/MEITU_OPENAPI_SECRET_KEY，或预置~/.meitu/credentials.json；仅在用户明确要求写入本地凭证时，再执行meitu config set-ak/meitu config set-sk
路径别名： 下文中
$VISUAL={OPENCLAW_HOME}/workspace/visual/
Core Workflow
Preflight → [Context: 跳过] → Execute (诊断 → 规划 → 逐步执行) → Deliver
↑ 工具型 skill，无创意上下文需求，始终跳过 Context
Preflight
meitu --version→ 未安装则提示npm install -g meitu-cli@latestmeitu auth verify --json→ 凭证无效则引导配置- Detect mode: cwd has
openclaw.yaml→ project mode; else → one-off can_record = cwd 有 openclaw.yaml AND $VISUAL 存在（两者缺一即 false） - Resolve output_dir: openclaw.yaml →
./output/| else →$VISUAL/output/meitu-image-fix/mkdir -p {output_dir}
Context
工具型 skill，无创意上下文需求，始终跳过 Context，直接到 Execute。
Execute
诊断：看图 + 听用户
从两个信息源判断问题：
视觉分析（用 Read 工具读取图片，多模态识别问题）：
| 观察到的现象 | 标记 |
|---|---|
| 分辨率低 / 明显模糊 / 压缩锯齿 / 噪点多 | quality:blur |
| 可见水印 / 半透明文字叠印 | content:watermark |
| 画面中有不属于主体的路人/杂物 | content:unwanted-object |
| 文字内容有错别字 | content:text-error |
| 背景有瑕疵（杂乱/破损/穿帮） | content:bg-flaw |
| 人脸可见 + 肤质粗糙/暗沉/痘印明显 | portrait:skin |
| 人脸可见 + 五官可优化 | portrait:feature |
用户意图解析（用户说的话直接映射到标签）：
| 用户表述 | 标记 |
|---|---|
| "变清晰""超清""高清""模糊""画质差""老照片" | quality:blur |
| "去水印""水印" | content:watermark |
| "去掉路人""去杂物""消除 XX" | content:unwanted-object |
| "改文字""改错字""把 X 改成 Y" | content:text-error |
| "背景修干净""背景杂乱" | content:bg-flaw |
| "磨皮""美颜""祛痘""提亮""皮肤" | portrait:skin |
| "变精致""五官调整" | portrait:feature |
| "去背景""抠图""透明背景" | cutout |
| "修一下""帮我处理一下"（模糊指令） | 完全依赖视觉分析 |
合并两个信息源，得到最终问题列表。
规划修复管线
执行顺序（硬约束——顺序错误会严重影响效果）：
Phase 1: image-superres-enhance 先提升画质，后续操作在清晰图上效果更好
Phase 2: image-edit / cutout 内容修复在高清底图上精度更高
Phase 3: image-edit(gummy_pro) 人像精修放最后，避免被前面步骤的重编码破坏
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.
- 12d ago First seen · 300 lines · 113 tokens per session scan A 6a052fec9043
meitu-image-fix is a skill published in the GitHub repository meitu/meitu-skills (32 stars, last pushed 15d ago), licensed MIT. It adds 113 tokens to every session and 4,241 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…