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 agentmods add skills/xyzbit/claude-plugins/platform-publishingnpx skills add xyzbit/claude-plugins --skill platform-publishinggit clone --depth 1 https://github.com/xyzbit/claude-pluginsWrote 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/xyzbit/claude-plugins/platform-publishing)<a href="https://agentmods.dev/skills/xyzbit/claude-plugins/platform-publishing"><img src="https://agentmods.dev/badge/skills/xyzbit/claude-plugins/platform-publishing.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00054 | $0.03632 |
| Opus 5 | $0.00027 | $0.01816 |
| Sonnet 5 | $0.00011 | $0.00726 |
| Haiku 4.5 | $0.00005 | $0.00363 |
Grade A, and why
platform-publishing 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 4d 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 — 557 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Publishing Skill
这是 content-create 插件的多平台发布指导。掌握此技能可以帮助你顺利将内容发布到微信公众号、小红书、飞书等平台。
支持的平台
1. 微信公众号 (wenyan-mcp)
特点:
- 深度长文为主（1500-3000 字）
- 专业、有深度的内容
- 重视排版和图文搭配
- 强互动（留言、讨论）
技术方案: 使用 wenyan-mcp（微信公众号 MCP 服务器）
发布方式: API 自动发布
2. 小红书 (playwright)
特点:
- 短文为主（<= 1000 字）
- 轻松、视觉化风格
- 爆款标题 + Emoji 排版
- 重视图片和互动
技术方案: 使用 playwright（浏览器自动化）
发布方式: 自动化发布到草稿箱，手动确认
3. 飞书 (lark-mcp)
特点:
- 中短文（800-1500 字）
- 简洁、实用的内容
- 工作场景为主
- 快速传阅
技术方案: 使用 lark-mcp（飞书 MCP 服务器）
发布方式: API 自动发布
发布流程
微信公众号发布
前置准备:
-
获取 API 凭证
- 登录微信公众平台：https://mp.weixin.qq.com/
- 开发 > 基本配置
- 获取 AppID 和 AppSecret
-
配置环境变量
export WECHAT_APP_ID="your-app-id" export WECHAT_APP_SECRET="your-app-secret" -
配置 MCP 服务器（已内置在插件中）
{ "wenyan-mcp": { "command": "npx", "args": ["-y", "@iflow-mcp/[email protected]"], "env": { "WECHAT_APP_ID": "${WECHAT_APP_ID}", "WECHAT_APP_SECRET": "${WECHAT_APP_SECRET}" } } }
发布操作:
方式 1: 通过工作流自动发布
/content-create:write "主题" platforms:wx
方式 2: 手动调用 MCP 工具
-
列出可用主题：
调用 wenyan-mcp 的 list_themes 工具 -
发布文章：
调用 wenyan-mcp 的 publish_article 工具 参数： - title: 文章标题 - content: 文章内容（Markdown） - theme: 主题名称（如 phycat）
输出:
- 成功：返回文章 URL
- 失败：返回错误信息
常见问题:
问题 1: 主题不存在
错误：Theme 'phycat' not found
解决：
- 调用
list_themes查看可用主题 - 选择其中一个主题使用
- 或不指定主题，使用默认主题
问题 2: API 凭证错误
错误：Invalid AppID or AppSecret
解决：
- 检查环境变量是否正确配置
- 确认 AppID 和 AppSecret 有效
- 重新获取凭证
问题 3: 发布频率限制
错误：API rate limit exceeded
解决：
- 微信公众号有发布频率限制
- 等待一段时间后重试
- 考虑手动发布
小红书发布
前置准备:
-
安装 Playwright（已内置在插件中）
{ "playwright": { "command": "npx", "args": ["@playwright/mcp@latest"] } } -
登录小红书账号（首次使用）
- 浏览器会自动打开
- 扫码或输入密码登录
- 登录状态会保存
发布操作:
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.
- 4d ago First seen · 557 lines · 54 tokens per session scan A 352fd30cb287
platform-publishing is a skill published in the GitHub repository xyzbit/claude-plugins (27 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 3,632 once invoked, about $0.0003 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…