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 tendhearth/wechat-cc --skill configuregit clone --depth 1 https://github.com/tendhearth/wechat-ccWrote 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/tendhearth/wechat-cc/configure)<a href="https://agentmods.dev/skills/tendhearth/wechat-cc/configure"><img src="https://agentmods.dev/badge/skills/tendhearth/wechat-cc/configure.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.1 | $0.00039 | $0.00506 |
| Opus 5 | $0.00019 | $0.00253 |
| Sonnet 5 | $0.00008 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
configure 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 6d 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
/wechat:configure — WeChat Channel Setup
Check status and guide login. Arguments passed: $ARGUMENTS
State lives under ~/.claude/channels/wechat/, with one sub-directory per bound account at accounts/<bot_id>/ containing token (bot bearer token, 0600) and account.json (botId, userId, baseUrl).
Status check (no args)
Read state files and show status:
-
Accounts — list
~/.claude/channels/wechat/accounts/. For each<bot_id>/sub-directory:- Check that both
tokenandaccount.jsonexist - Read
account.jsonand showbotId,userId,baseUrl - If
tokenexists, show its first 10 chars masked (e.g.abcdef1234…)
- Check that both
-
Access — read
~/.claude/channels/wechat/access.json(missing = defaults:allowlist, empty). Show:- DM policy (
allowlistordisabled) - Allowed senders: count and list
- DM policy (
-
What next based on state:
- No accounts → "No accounts bound yet. Run
wechat-cc setupin a terminal to scan the QR code." - Accounts bound, nobody allowed → "Accounts are bound but the allowlist is empty. The scanner is normally auto-added on login; if not, add manually:
/wechat:access allow <user_id>" - Accounts bound, allowlist populated → "Ready. Messages from allowed users will reach this session. Start with
wechat-cc run."
- No accounts → "No accounts bound yet. Run
Re-login / add another account
Tell the user to run wechat-cc setup in a terminal. Each successful scan creates a new accounts/<bot_id>/ directory — running setup again does not overwrite existing accounts, it appends. To remove a stale account, delete its accounts/<bot_id>/ directory.
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.
- 6d ago First seen · 41 lines · 39 tokens per session scan A 5d0a91677b28
configure is a skill published in the GitHub repository tendhearth/wechat-cc (6 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 506 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-31.
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…