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 video-denoise-enhancegit 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/video-denoise-enhance)<a href="https://agentmods.dev/skills/meitu/meitu-skills/video-denoise-enhance"><img src="https://agentmods.dev/badge/skills/meitu/meitu-skills/video-denoise-enhance/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/video-denoise-enhance"><img src="https://agentmods.dev/badge/skills/meitu/meitu-skills/video-denoise-enhance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 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 17 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 20 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.00076 | $0.01173 |
| Opus 5 | $0.00038 | $0.00587 |
| Sonnet 5 | $0.00015 | $0.00235 |
| Haiku 4.5 | $0.00008 | $0.00117 |
Grade A, and why
video-denoise-enhance 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.
What it actually says
Video Denoise Enhance
Overview
去除视频颗粒感 / 色块 / 运动噪声，保留细节同时降噪。覆盖高感光拍摄降噪、暗光拍摄噪点消除、老视频颗粒修复、游戏/运动视频色块修复。噪点越严重效果越明显；非噪点问题（模糊、欠曝、分辨率低）使用本工具无效。
不处理：综合画质修复、视频超分、夜景暗部提亮、图片去噪、补帧 / 流畅度。
API Mapping
| 场景 | API name |
|---|---|
| 视频去噪 | video_denoise_enhance |
Dependencies
- meitu-cli:
>=2.0.6 - 凭证：CONFIG AKSK →
meitu tools update；EXEC AKSK → 跑命令 - 环境变量：
MEITU_OPENAPI_TOOL_TASK_MODE=command
路径别名：
$VISUAL={OPENCLAW_HOME}/workspace/visual/
Core Workflow
Preflight → Execute → Deliver
Preflight
meitu --version与meitu auth verify --json- 检测
MEITU_OPENAPI_TOOL_TASK_MODE=command - output_dir：项目 →
./output/；一次性 →$VISUAL/output/video-denoise-enhance/；mkdir -p
Execute
触发信号与路由
| 用户原话 | 路由 |
|---|---|
| 去噪 / 降噪 / 去颗粒 / 噪点太多 / 杂色 / ISO 太高 | video_denoise_enhance |
| "视频干净一点"（意图模糊） | 轻确认"是去噪点，还是做整体画质修复？" |
单 API 工具：参数齐全即调用，失败重试 1 次后返回错误，不做跨工具兜底。
参数定义
| 参数 | 类型 | 必填 | 范围 | 默认 | 说明 |
|---|---|---|---|---|---|
video_url |
STRING | 是 | — | — | 视频地址 |
说明：本工具仅使用 video_url，不需要 prompt。
工具调用
meitu video-denoise-enhance --video_url {url} --json --download-dir {output_dir} --skill_name skill_video-denoise-enhance
错误降级
| 场景 | 处理 |
|---|---|
video_url 缺失 |
提示"请提供视频链接" |
video_url 不可访问 |
不重试，提示"请提供有效视频链接" |
| 视频噪点不明显但用户坚持 | 正常调用，告知效果可能不明显 |
| API 调用失败 / 超时 | 重试 1 次，仍失败返回错误 |
| 内容合规拦截 | 直接返回合规提示，不重试 |
| 输入为图片 | 拒绝，仅支持视频 |
Deliver
mv {file} {output_dir}/{date}_{name}_denoise.mp4
Output
- 格式：MP4
- 命名：
{YYYY-MM-DD}_{descriptive-name}_denoise.mp4 - 位置：项目 →
./output/；一次性 →$VISUAL/output/video-denoise-enhance/
基线 Task ID
t_mt1a3i5n7b96af8209-02f2-41b3-9038-6f5a44e83f31
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 · 113 lines · 76 tokens per session scan A 486b02fcd48c
video-denoise-enhance is a skill published in the GitHub repository meitu/meitu-skills (32 stars, last pushed 15d ago), licensed MIT. It adds 76 tokens to every session and 1,173 once invoked, about $0.0004 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…