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-adaptgit 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-adapt)<a href="https://agentmods.dev/skills/meitu/meitu-skills/meitu-image-adapt"><img src="https://agentmods.dev/badge/skills/meitu/meitu-skills/meitu-image-adapt/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-adapt"><img src="https://agentmods.dev/badge/skills/meitu/meitu-skills/meitu-image-adapt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 7 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 9 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 11 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 38 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 144 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.
- medium Rogue Agent · line 19 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.00093 | $0.02153 |
| Opus 5 | $0.00046 | $0.01077 |
| Sonnet 5 | $0.00019 | $0.00431 |
| Haiku 4.5 | $0.00009 | $0.00215 |
Grade A, and why
meitu-image-adapt 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 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.
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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
将用户提供的图片智能适配到目标宽高（像素），主体保持不变形，背景自然延展无接缝。核心工具为 meitu image-transform 的画布扩展能力。
Dependencies
- meitu-cli (>=2.0.6):
npm install -g meitu-cli@latest- 首选环境变量：
MEITU_OPENAPI_ACCESS_KEY/MEITU_OPENAPI_SECRET_KEY - 或预置凭证文件：
~/.meitu/credentials.json - 如需人工初始化本地凭证，可显式执行
meitu config set-ak --value "..."+meitu config set-sk --value "..."（会写入本地文件） - 验证:
meitu auth verify --json
- 首选环境变量：
路径别名:
$VISUAL={OPENCLAW_HOME}/workspace/visual/
Core Workflow
Preflight → Execute → Deliver
Preflight
meitu --version→ 未安装则提示npm install -g meitu-cli@latestmeitu auth verify --json→ 凭证无效则提示配置 AK/SK- Detect mode: cwd has
openclaw.yaml→ project mode; else → one-off - Resolve output_dir: openclaw.yaml →
./output/| else →$VISUAL/output/meitu-image-adapt/mkdir -p {output_dir}
Execute
1. 收集输入
| 输入 | 说明 | 必填 | 默认值 |
|---|---|---|---|
| image | 待适配的原图 | 是 | — |
| width | 目标宽度（像素） | 是 | 1080 |
| height | 目标高度（像素） | 是 | 1920 |
image 接受格式： URL 或本地路径 (.jpg/.jpeg/.png/.webp)
2. 目标尺寸解析
用户可能直接给像素值，也可能说平台名或比例。按以下优先级解析：
A. 用户给了明确像素 → 直接使用。
B. 用户给了平台名 → 查 references/platform-presets.md 获取推荐尺寸。
常用速查（完整表见 references）：
| 平台 | 场景 | width × height |
|---|---|---|
| 小红书 | 竖版笔记封面 | 1080 × 1440 |
| 抖音 | 竖版视频封面 | 1080 × 1920 |
| 微信公众号 | 文章头图 | 900 × 383 |
| 微信朋友圈 | 正方形 | 1080 × 1080 |
| B站 | 视频封面 | 1920 × 1080 |
| 淘宝 | 商品主图 | 800 × 800 |
若平台有多个场景，列出选项让用户选择。
C. 用户给了比例（如 16:9） → 保证输出覆盖原图所有像素（不裁切），取能包含原图的最小目标尺寸：
- 对目标比例 W:H，分别计算两种方案：① 以原图宽度为基准算高度；② 以原图高度为基准算宽度。取两者中输出面积更大的方案（即确保两边都 ≥ 原图）。
- 例：原图 1080×1440，目标 16:9 → 方案① width=1080, height=608（高度缩小，丢内容）；方案② width=2560, height=1440（宽度延展，保全内容）→ 取方案② = 2560×1440
- 例：原图 1080×1440，目标 1:1 → width=1440, height=1440（以长边为基准，短边延展）
D. 用户未指定 → 默认 1080×1920（竖版全屏），并告知用户可调整。
3. 输入预检
调用前检查，避免浪费额度：
- 原图可访问 — URL 能打开 / 本地路径存在
- 目标尺寸合理 — width 和 height 均在 100-8192 范围内
- 非无意义操作 — 目标尺寸与原图尺寸差异 ≥5%（几乎相同则提醒用户确认）
- 延展比例合理 — 单方向延展不超过原图 4 倍（如 500px 延展到 2000px 以上），超出则警告质量可能下降
What ships with it
1 file beside SKILL.md 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.
- 12d ago First seen · 172 lines · 93 tokens per session scan A f1df026bbb2e
meitu-image-adapt is a skill published in the GitHub repository meitu/meitu-skills (32 stars, last pushed 15d ago), licensed MIT. It adds 93 tokens to every session and 2,153 once invoked, about $0.0005 per session on Opus 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.
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…