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 HeroAshacker/wechat-content-pipeline --skill wechat-pipelinegit clone --depth 1 https://github.com/HeroAshacker/wechat-content-pipelineWrote 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/heroashacker/wechat-content-pipeline/wechat-pipeline)<a href="https://agentmods.dev/skills/heroashacker/wechat-content-pipeline/wechat-pipeline"><img src="https://agentmods.dev/badge/skills/heroashacker/wechat-content-pipeline/wechat-pipeline/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/heroashacker/wechat-content-pipeline/wechat-pipeline"><img src="https://agentmods.dev/badge/skills/heroashacker/wechat-content-pipeline/wechat-pipeline.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00143 | $0.04300 |
| Opus 5 | $0.00072 | $0.02150 |
| Sonnet 5 | $0.00029 | $0.00860 |
| Haiku 4.5 | $0.00014 | $0.00430 |
Grade A, and why
wechat-pipeline 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 10d 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
微信公众号全流程编排器 (wechat-pipeline)
⚠️ 强制执行协议 (MUST READ FIRST)
Pipeline 启动后，Claude 必须连续自动执行，不得在确认点以外的任何地方暂停。
绝对禁止行为（违反即错误）
- ❌ 禁止在门禁评估后展示结果并等待用户反馈，直接进入下一轮或继续
- ❌ 禁止在门禁每轮之间停顿，评估→修改→评估必须连续执行
- ❌ 禁止说"已完成第N轮评估，是否继续？"——直接执行下一轮
- ❌ 禁止说"评估结果：XX分，要我帮你修改吗？"——不达标立即修改
- ❌ 禁止完成全文后问"要进行质量门禁吗？"——自动进入
- ❌ 禁止门禁通过后问"要排版吗？"——等确认点3后自动排版
- ❌ 禁止3个确认点以外的任何中间询问或停顿
- ❌ 禁止说"下一步我将..."然后停下——直接执行
唯一合法停顿点
| 模式 | 确认点 |
|---|---|
| 完整流程 | 确认点1（选题）、确认点2（大纲）、确认点3（终稿） |
| --from-draft | 仅确认点3（终稿质量报告） |
| --from-topic | 确认点1（选题）、确认点2（大纲）、确认点3（终稿） |
入口模式
| 模式 | 命令 | 说明 |
|---|---|---|
| 完整流程 | /wechat-pipeline "主题" --type opinion |
从选题开始 |
| 从选题开始 | /wechat-pipeline --from-topic |
先获取热点再选题 |
| 从草稿开始 | /wechat-pipeline --from-draft article.md |
跳过写作，直接进门禁 |
参数
| 参数 | 默认值 | 说明 |
|---|---|---|
| topic | 无 | 主题/方向/想法 |
| --type | opinion | 文章类型 (opinion/tutorial/listicle/commentary/story) |
| --provider | gemini | AI provider |
| --from-topic | false | 从选题阶段开始 |
| --from-draft | 无 | 从已有草稿进入门禁循环 |
| --theme | simple | 排版主题 |
| --max-rounds | 3 | 门禁最大迭代轮数 |
完整流程 (6 阶段)
阶段 1: 选题 (wechat-topic)
触发: 完整流程 或 --from-topic
cd ~/projects/agents-bc376a3719/🧪\ 小项目与测试/wx-format
node index.js topic --niche "<主题关键词>" --analyze --format structured --output /tmp/pipeline-topic.json
读取 /tmp/pipeline-topic.json，向用户展示 AI 推荐的 5 个选题。
🔴 确认点 1: 用户确认选题方向
- 展示推荐选题列表
- 用户选择一个方向，或提供自己的方向
- 记录确认的选题到
$PIPELINE_TOPIC - 用户回复后立即进入阶段2，不要说"好的，开始写大纲"之类的过渡语，直接输出大纲
阶段 2: 写作 - 大纲 (wechat-writer --outline-only)
node index.js write "$PIPELINE_TOPIC" --type <type> --provider <provider> \
--outline-only --title-candidates 5 --no-confirm -o /tmp/pipeline-outline.md
🔴 确认点 2: 用户确认大纲
- 展示大纲 + 5 个标题候选
- 用户选择标题或提供自己的标题
- 用户可调整大纲结构
- 用户回复后立即进入阶段3，直接开始写全文
阶段 3: 写作 - 全文 (wechat-writer)
node index.js write "$PIPELINE_TOPIC" --type <type> --provider <provider> \
--no-confirm -o /tmp/pipeline-draft.md
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.
- 10d ago First seen · 352 lines · 143 tokens per session scan A d905188365ea
wechat-pipeline is a skill published in the GitHub repository HeroAshacker/wechat-content-pipeline (12 stars, last pushed 6mo ago), licensed MIT. It adds 143 tokens to every session and 4,300 once invoked, about $0.0007 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…