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-sheetnpx skills add WecomTeam/wecom-cli --skill wecomcli-sheetgit 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.00130 | $0.02232 |
| Opus 5 | $0.00065 | $0.01116 |
| Sonnet 5 | $0.00026 | $0.00446 |
| Haiku 4.5 | $0.00013 | $0.00223 |
Grade A, and why
wecomcli-sheet 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-sheet — 98% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
企业微信在线表格管理
执行任何
wecom-cli命令前，必须先读取并完成wecomcli-shared技能的公共前置检查。
资源型 skill，负责在线表格（sheet）的新建、导入与内容读写及子表管理。
适用范围
适用
- 新建 / 导入企微在线表格
- 读取 / 修改 / 追加在线表格内容
- 添加 / 删除在线表格子表
不适用
- 搜索文档 / 修改文档权限 / 重命名 / 加成员 → 改用
wecomcli-doc-manage - 用户给的链接是
https://doc.weixin.qq.com/smartsheet/...→ 改用wecomcli-smartsheet - 若遇到的
docid以s3开头（形如s3_xxxx）→ 改用wecomcli-smartsheet
接口路由表
硬规则：第二列是
references/xxx.md链接的, 命中这一行后先read对应 references 文件，再构造命令。
| 用户意图 | 参考位置 |
|---|---|
| 新建在线表格 | 见下方「新建在线表格」 |
| 导入本地 CSV / Excel 文件为企微在线表格 | 见下方「导入在线表格」 |
| 读取在线表格基础信息与子表列表 | 见下方「读取在线表格」 |
| 读取在线表格子表数据 | references/sheet-ranges-get.md |
| 修改在线表格指定区域内容 | references/sheet-contents-update.md |
| 在线表格末尾追加一行数据 | references/sheet-rows-append.md |
| 添加在线表格子工作表 | references/sheet-subsheets-add.md |
| 删除在线表格子工作表 | references/sheet-subsheets-delete.md |
接口详述
新建在线表格
从零新建一篇企微在线表格：空白，或带初始数据（二维表格数据）。本接口不接受任何文件路径参数——"用本地文件建/导入"走「导入在线表格」。
命令
wecom-cli sheet create --json '<JSON 参数>'
参数
| 字段 | 类型 | 必填 | 默认值 | 语义 |
|---|---|---|---|---|
doc_name |
string | 是 | — | 表格标题 |
grid_data |
object | 否 | — | 默认子表初始化数据；子结构见下方 |
grid_data 对象结构：
| 子字段 | 类型 | 必填 | 默认值 | 语义 |
|---|---|---|---|---|
start_row / start_column |
int | 否 | 0 |
起始行 / 列号，从 0 起 |
rows |
array | 否 | — | 各行数据；每项 values 为单元格数组 |
rows[].values[].cell_value |
object | 否 | — | 单元格值，见下方「cell_value 类型选择」 |
rows[].values[].data_type |
string | 否 | — | 枚举：TEXT / NUMBER / LINK / FORMULA |
cell_value 类型选择
硬规则：选择
cell_value形态后，必须同时把同级的data_type设置为下表对应值。
| 形态 | 对应 data_type |
结构 | 适用场景 |
|---|---|---|---|
text |
TEXT |
{"text": "<纯文本>"} |
纯文本内容（如姓名、说明、标签、编号字符串等） |
number |
NUMBER |
{"number": 123.45} |
数值，用于金额、数量、比率等需要参与公式计算或聚合的数据；值为 JSON 数字类型，不加引号 |
formula |
FORMULA |
{"formula": "=SUM(A1,A2)"} |
任何以 = 开头的公式，包括 =SUM(...)、=A1+B1、=IF(...)、=VLOOKUP(...) 等 |
link |
LINK |
{"link": {"url": "<URL>", "text": "<显示文本>"}} |
超链接 |
What ships with it
5 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 · 173 lines · 130 tokens per session scan A cfb9b073af21
wecomcli-sheet is a skill published in the GitHub repository WecomTeam/wecom-cli (2,997 stars, last pushed 7d ago), licensed MIT. It adds 130 tokens to every session and 2,232 once invoked, about $0.0006 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.