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-calendarnpx skills add WecomTeam/wecom-cli --skill wecomcli-calendargit clone --depth 1 https://github.com/WecomTeam/wecom-cliWrote 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/wecomteam/wecom-cli/wecomcli-calendar)<a href="https://agentmods.dev/skills/wecomteam/wecom-cli/wecomcli-calendar"><img src="https://agentmods.dev/badge/skills/wecomteam/wecom-cli/wecomcli-calendar.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 | $0.00155 | $0.08158 |
| Opus 5 | $0.00077 | $0.04079 |
| Sonnet 5 | $0.00031 | $0.01632 |
| Haiku 4.5 | $0.00015 | $0.00816 |
Grade A, and why
wecomcli-calendar 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 4d 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-calendar — 100% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
企业微信日程技能
执行任何
wecom-cli命令前，必须先读取并完成wecomcli-shared技能的公共前置检查。
适用范围
适用
- 预约 / 创建日程（含纯线下面对面碰头，即不带在线会议链接的安排）
- 查看 / 浏览日程（今天有什么安排、查本周日程）
- 搜索日程（按关键词、按组织人、按参与人找某个日程）
- 更新 / 修改日程（改时间、改地点、加减人、换会议室；不支持更新周期日程）
- 取消日程（不支持取消周期日程）
- 查忙闲 / 约多人共同空闲时段
- 订会议室、查会议室空不空、查办公楼
不适用
- 创建、更新、取消周期 / 重复日程（每周 / 每月 / 每天重复）→ 均不支持，引导用户在企业微信客户端手动操作
- 回复 / 拒绝日程邀请（接受 / 拒绝 / 待定，含"拒绝这个日程""不参加"）→ 不支持，引导用户在企业微信客户端操作或私信发起人
易混淆场景路由
- 用户要创建含在线会议链接的会议（需会议号 / 入会链接 / 远程或视频参会）→ 改用
wecomcli-meeting（创建会议会同时生成日程，无需在本技能再建） - 用户仅说"开会 / 约个会 / 安排个会 / xx 会"等、未明确是日程还是在线会议（创建场景）→ 必须先用文字追问消歧（固定问题"需要创建日程还是会议？"，请用户回复"日程 / 会议"），不得臆断直接创建
- 用户要的会同时支持线下与远程参会（如"线下开、外地同事远程接入"）→ 含在线会议链接，改用
wecomcli-meeting - 仅给了地点 / 会议室号（如"在 1605 开会""订个会议室开会"）→ 不构成"明确是日程"，仍需先用文字询问消歧，不能因带地点就跳过追问
- 查询场景的模糊表述（"最近有什么会 / 有哪些会"）→ 严禁追问，日程和会议都查并合并展示；仅当明确提到"在线会议 / 视频会议 / 入会链接 / 会议号 / 腾讯会议 / 远程参会"时才改用
wecomcli-meeting只查会议
路由规则
| 用户意图 | 参考文档 |
|---|---|
| 预约日程、安排纯线下面对面会议（不含在线会议链接）、创建日程 | calendar-create |
| 看日程、今天有什么安排、查本周日程 | calendar-agenda |
| 找某个日程、项目评审是什么时候 | calendar-search |
| 查日程详情、看周期规则、看会议链接 | calendar-agenda |
| 取消日程、不开了 | calendar-cancel |
| 修改日程、更新日程、改时间、加人/移除人、换会议室 | calendar-update |
| 查忙闲、某人什么时候有空、约多人共同空闲 | calendar-freebusy |
| 订会议室、查会议室空不空、查办公楼、约会议室 | calendar-meeting-room |
浏览 vs 搜索的选择原则：用户提到日程主题关键词时走搜索；只给了时间/日期而无日程主题关键词时，必须走列表浏览（
list）。需要周期规则、会议链接等详情时再读取单条日程详情补充。
技能边界：日程 vs 会议 [CRITICAL]
本技能（wecomcli-calendar）只负责日程——即非会议的日程安排，以及不含在线会议链接的纯线下面对面会议。只要涉及在线会议链接（含远程/视频参会）的会议，一律归 wecomcli-meeting 技能，不在本技能创建。
| 用户意图 | 归属技能 |
|---|---|
| 预约日程、安排纯线下面对面会议（不含在线会议链接）、订会议室、查/改/取消日程、查忙闲 | 本技能 wecomcli-calendar |
| 创建含在线会议链接的会议、需要会议号或入会链接的会、需要远程/视频参会的会 | wecomcli-meeting 技能 |
What ships with it
7 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.
- 4d ago First seen · 304 lines · 155 tokens per session scan A badfe3239dda
wecomcli-calendar is a skill published in the GitHub repository WecomTeam/wecom-cli (3,014 stars, last pushed 9d ago), licensed MIT. It adds 155 tokens to every session and 8,158 once invoked, about $0.0008 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…