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 appleweiping/WEIPING_WIKI --skill wechat-video-channel-publishgit clone --depth 1 https://github.com/appleweiping/WEIPING_WIKIWrote 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/appleweiping/weiping_wiki/wechat-video-channel-publish)<a href="https://agentmods.dev/skills/appleweiping/weiping_wiki/wechat-video-channel-publish"><img src="https://agentmods.dev/badge/skills/appleweiping/weiping_wiki/wechat-video-channel-publish/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/appleweiping/weiping_wiki/wechat-video-channel-publish"><img src="https://agentmods.dev/badge/skills/appleweiping/weiping_wiki/wechat-video-channel-publish.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 MCP Rug Pull · line 36 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00049 | $0.00754 |
| Opus 5 | $0.00024 | $0.00377 |
| Sonnet 5 | $0.00010 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
wechat-video-channel-publish 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 8d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WeChat Video Channel Publish
This skill packages a focused 微信视频号 publishing workflow for local agent execution.
Use it when the task is specifically about:
- 视频号扫码登录
- 上传短视频
- 设置标题、标签、正文长描述
- 设置封面图
- 定时发布
- 保存草稿（best effort；平台 UI 可能在部分状态下拒绝）
- 发布后补评论
Quick Start
- Read
references/runtime-requirements.md. - Build the CLI if
dist/cli.jsdoes not exist. - Run
tencent loginortencent check. - Run
tencent uploadwith absolute video and cover paths. - If the task uses a publishing queue, first normalize it into direct CLI arguments.
- Before any public repo push, read
references/privacy-checklist.md.
Workflow
Step 1: Prepare Runtime
- Run all commands in the repo root.
- If needed, execute:
npm installnpx playwright install chromiumnpm run build
Step 2: Login or Reuse Cookie
- For first-time login:
node dist/cli.js tencent login --account <name>
- For validation:
node dist/cli.js tencent check --account <name>
The cookie file is stored outside the repo by default and must never be committed.
Step 3: Publish a Video
- Read
references/publish-workflow.md. - Use absolute paths for
--fileand--cover. - Supported fields:
--title--tags--caption--cover--pinned-comment--schedule--category--draft
Step 4: Validate Carefully
- Prefer
--draftwhen verifying a new selector path or runtime change, but do not combine it with--schedule. - Treat
coverandpinned-commentas runtime-sensitive features. - If UI changes break these steps, keep login and upload logic intact and narrow the failure to the affected selector flow.
Step 5: Repo Hygiene
- Keep cookies, screenshots, local logs, and temporary exports out of git.
- When sharing publicly, include only reusable code, templates, and references.
Resource Loading Rules
- Read
references/runtime-requirements.mdbefore execution. - Read
references/publish-workflow.mdwhen mapping a publishing plan into CLI arguments. - Read
references/privacy-checklist.mdbefore creating or updating a public repository.
What ships with it
19 files 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.
- .gitignore 97 B
- agents/openai.yaml 254 B
- assets/publish-command.example.txt 300 B
- package-lock.json 19 KB
- package.json 682 B
- README.md 1.8 KB
- references/privacy-checklist.md 529 B
- references/publish-workflow.md 1.0 KB
- references/runtime-requirements.md 461 B
- scripts/tencent_delete_scheduled.ts 3.4 KB runs code
- scripts/tencent_inspect_scheduled.ts 2.5 KB runs code
- src/browser.ts 3.3 KB runs code
- src/cli.ts 3.3 KB runs code
- src/config.ts 826 B runs code
- src/paths.ts 908 B runs code
- src/platforms/tencent.ts 33 KB runs code
- src/progress.ts 263 B runs code
- src/stealth.min.js 176 KB runs code
- tsconfig.json 311 B
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.
- 8d ago First seen · 96 lines · 49 tokens per session scan A cd97a4f5982b
wechat-video-channel-publish is a skill published in the GitHub repository appleweiping/WEIPING_WIKI (122 stars, last pushed 16d ago), licensed MIT. It adds 49 tokens to every session and 754 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
feature-demo-recording
Record a demo video of a web feature from a real browser. Two modes -- a NARRATED film where measured voiceover drives the timeline (designed slides, subtitles, punch-in camera, rendered from an HTML timeline), and a SILENT evidence clip for a PR or a QA pass. Use when the user asks to record a video, demo, or screen…
html-to-video-pipeline
Reliable HTML-to-MP4 rendering via headless browser recording (Playwright/Puppeteer) + ffmpeg — the ordering, gotchas, and verification steps you MUST get right or the output silently rots. Trigger whenever the user is building or debugging any pipeline that turns an HTML/CSS/JS page (single-file, multi-composition…
browser-video-recording
Create polished 60 fps 4:3 4K browser screen-recording style videos from Codex in-app browser captures, with browser-only crop, natural macOS cursor styling, deliberate click choreography, zoom-follow framing, ffprobe/thumbnail verification, and optional native recording compatibility checks. Use when the user asks to…
record-video
Record and upload a short browser interaction video artifact.
playwright-recording
Record browser interactions as video using Playwright. Use for capturing demo videos, app walkthroughs, and UI flows for Remotion videos. Triggers include recording a demo, capturing browser video, screen recording a website, or creating walkthrough footage.
playwright-recording
Record browser interactions as video using Playwright. Use for capturing demo videos, app walkthroughs, and UI flows for Remotion videos. Triggers include recording a demo, capturing browser video, screen recording a website, or creating walkthrough footage.