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 vibeinging/YiYi --skill wechat_writergit clone --depth 1 https://github.com/vibeinging/YiYiWrote 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/vibeinging/yiyi/wechat_writer)<a href="https://agentmods.dev/skills/vibeinging/yiyi/wechat_writer"><img src="https://agentmods.dev/badge/skills/vibeinging/yiyi/wechat_writer/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/vibeinging/yiyi/wechat_writer"><img src="https://agentmods.dev/badge/skills/vibeinging/yiyi/wechat_writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.01079 |
| Opus 5 | $0.00023 | $0.00540 |
| Sonnet 5 | $0.00009 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
wechat_writer 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 9d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WeChat Official Account Writer (公众号写作)
Help users create high-quality articles for WeChat Official Accounts, covering research, writing, formatting, and optimization for the WeChat reading experience.
When to Activate
Trigger conditions:
- User mentions 公众号: "写公众号文章", "公众号发布", "微信文章"
- User asks to write articles for WeChat: "帮我写一篇文章", "写一篇关于XX的文章"
- User asks to format content for WeChat: "排版", "美化文章", "公众号格式"
- User wants to research and write: "研究XX然后写篇文章"
Workflow
Stage 1: Topic Research & Planning
-
Clarify topic and angle: Ask the user for:
- Topic/subject matter
- Target audience (tech developers, product managers, general readers, etc.)
- Tone (professional, conversational, storytelling, etc.)
- Approximate length (short: 1500-2000 words, medium: 2000-4000 words, long: 4000+ words)
-
Research: Use browser_use to:
- Search for latest information, data, and trends on the topic
- Find authoritative sources and references
- Identify unique angles not yet covered
Stage 2: Writing
Follow WeChat article best practices:
Structure
- Hook title (标题): Compelling, under 30 characters, use numbers or questions when appropriate
- Opening (开头): Hook the reader in the first 3 sentences — use a story, question, surprising fact, or pain point
- Body (正文): Clear sections with subheadings, short paragraphs (2-4 sentences), mix of text and visual breaks
- Conclusion (结尾): Summarize key takeaways, include call-to-action (关注, 点赞, 在看, 转发)
Writing Style for WeChat
- Use conversational Chinese, avoid overly academic language
- Short paragraphs — WeChat is read on mobile, dense text loses readers
- Use bold for key points
- Add section dividers for visual rhythm
- Include relatable examples and analogies
- Use rhetorical questions to engage readers
- Add emoji sparingly for visual accent (not excessive)
Content Types
Tech/AI Articles (技术科普):
- Explain complex concepts with analogies
- Include real-world use cases and demos
- Add code snippets if relevant (keep short)
- Reference official sources and papers
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.
- 9d ago First seen · 127 lines · 45 tokens per session scan A ec3f298a6852
wechat_writer is a skill published in the GitHub repository vibeinging/YiYi (51 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 1,079 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-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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…