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/wecomteam/wecom-cli/wecomcli-docnpx skills add WecomTeam/wecom-cli --skill wecomcli-docgit clone --depth 1 https://github.com/WecomTeam/wecom-cliWhat 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.00228 | $0.01907 |
| Opus 5 | $0.00114 | $0.00954 |
| Sonnet 5 | $0.00046 | $0.00381 |
| Haiku 4.5 | $0.00023 | $0.00191 |
Grade A, and why
wecomcli-doc 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- wecomcli-doc — 95% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
企业微信doc文档管理
执行任何
wecom-cli命令前，必须先读取并完成wecomcli-shared技能的公共前置检查。
资源型 skill，负责doc文档（doc）的新建、导入与内容读写。
适用范围
适用
- 新建 / 导入企微 doc 文档
- 读取 doc 文档内容
- 向 doc 文档追加一行 / 覆盖写入doc 文档
不适用
- 搜索文档 / 修改文档权限 / 重命名 / 加成员 → 改用
wecomcli-doc-manage
易混淆场景路由
- 用户说"创建文档 / 写文档 / 整理成文档" 且未指定 doc 类型 → 改用
wecomcli-smartpage（智能文档为默认） - 用户给的链接是
https://doc.weixin.qq.com/smartpage/...或者https://page.weixin.qq.com/smartpage/...→ 改用wecomcli-smartpage - 若遇到的
docid以a1或者b1开头（形如a1_xxxx,b1_xxxx）→ 改用wecomcli-smartpage
接口路由表
路由表第二列若是 references/xxx.md 链接 → 必须先用 read 工具读完该文件，再构造命令。
| 用户意图 | 参考位置 |
|---|---|
| 新建doc文档（在线） | 见下方「新建doc文档」 |
| 导入本地文件为企微doc文档 | 见下方「导入doc文档」 |
| 读取doc文档内容 | 见下方「读取doc文档内容」 |
| 追加文本到doc文档末尾 | +contents-append |
| 全量覆盖doc文档内容 | +contents-overwrite |
写入语义裁定（追加 vs 覆盖）
- 默认追加：用户用「写入 / 写到 / 记录 / 补充 / 加进去 / 记一下」等中性动词，且未明确要求清空或替换时，一律走
append（追加，不破坏原有内容）。 - 仅显式覆盖：仅当用户明确出现「覆盖 / 重写 / 替换 / 清空重写 / 整个换成」等强语义词时，才走
overwrite。
接口详述
新建doc文档
新建企微doc文档统一走「生成 .docx → 导入」两步流程：
- 生成
.docx文件：按 +doc-create 生成.docx文件。 - 导入为企微doc文档：使用下方「导入doc文档」接口将生成的
.docx文件导入为企微doc文档。注意import导入的时候file_name应和文档标题保持一致。
导入doc文档
把本地文件（.doc / .docx / .txt）导入为企微doc文档。
命令
wecom-cli doc import --json '<JSON 参数>'
参数
| 字段 | 类型 | 必填 | 默认值 | 语义 |
|---|---|---|---|---|
doc_type |
string | 是 | doc |
固定为 doc（doc文档） |
file_name |
string | 是 | — | 二进制文件名（含后缀），用于业务判断源文件类型 |
file_path |
string | 是 | — | 源文件的本地绝对路径 |
passwd |
string | 否 | — | Office 文件加密密码（若有） |
返回
| 字段 | 类型 | 说明 |
|---|---|---|
docid |
string | 导入完成后的文档 ID |
url |
string | 导入完成后的访问链接 |
task_status |
string | 任务状态枚举，如 succ 成功 |
What ships with it
4 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.
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.
- 2d ago First seen · 138 lines · 228 tokens per session scan A 761a5cd36f3b
wecomcli-doc is a skill published in the GitHub repository WecomTeam/wecom-cli (2,997 stars, last pushed 8d ago), licensed MIT. It adds 228 tokens to every session and 1,907 once invoked, about $0.0011 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…