Lark CLI is a command-line tool for using Lark/Feishu services such as messaging, documents, spreadsheets, calendars, mail, tasks, and meetings. It is intended for people and AI agents that need to work with these business tools through terminal commands.
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/larksuite/cli/lark-calendarnpx skills add larksuite/cli --skill lark-calendargit clone --depth 1 https://github.com/larksuite/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/larksuite/cli/lark-calendar)<a href="https://agentmods.dev/skills/larksuite/cli/lark-calendar"><img src="https://agentmods.dev/badge/skills/larksuite/cli/lark-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.00092 | $0.04816 |
| Opus 5 | $0.00046 | $0.02408 |
| Sonnet 5 | $0.00018 | $0.00963 |
| Haiku 4.5 | $0.00009 | $0.00482 |
Grade A, and why
lark-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 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
4 near-identical copies found in the catalogue:
- lark-calendar — 92% identical, 86 lines differ
- lark-calendar — 89% identical, 79 lines differ
- lark-calendar — 89% identical, 94 lines differ
- lark-calendar — 88% identical, 108 lines differ
How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
calendar (v4)
开始前先读 ../lark-shared/SKILL.md（认证、权限处理）。
CRITICAL — 凡涉及预约日程/会议室、调整时间或查询/搜索会议室，第一步 MUST 读 references/lark-calendar-schedule-meeting.md。仅编辑字段（改标题/描述）或增删参会人（不涉及时间和会议室）时可跳过，直接读 references/lark-calendar-update.md。
身份
按日程归属选身份：
- 查看/管理登录用户本人的日程 →
--as user（默认，绝大多数场景）。 - 查看/管理 bot 自己创建/拥有的日程 →
--as bot
对话人称映射：「我」= 登录用户，「你」= 应用（bot）；作为字段取值的人称（参会人、会议 owner 等）不参与身份判定，如「你创建日程，邀请我、会议 owner 为我」→ --as bot 创建，登录用户仅作参会人与会议 owner。
# 用户本人日程 → user
lark-cli calendar +agenda --as user
# bot 自建或参与的日程 → bot
lark-cli calendar +agenda --as bot
Shortcuts
| Shortcut | 说明 |
|---|---|
+agenda |
查看日程安排（默认今天） |
+meeting |
通过日程事件 ID 获取关联的视频会议信息（meeting_id、meeting_note），日程开过视频会议才会有meeting_id,注意: 视频会议链接获取走+get命令 |
+create |
创建日程并邀请参会人（ISO 8601 时间） |
+update |
更新既有日程字段，或独立增量添加/移除参会人和会议室；重复性日程/例外必须传 --apply-to（详见 重复性日程操作规范） |
+delete |
删除日程；重复性日程/例外必须传 --apply-to（详见 重复性日程操作规范） |
+freebusy |
查询主日历的忙闲/RSVP状态/空闲时间段。(如需预约/推荐时间段走 +suggestion——它综合工作时间、忙碌区间和休息时间推荐。) |
+room-find |
针对一个或多个明确的时间块查找可用会议室（无明确时间时禁止直接调用，需先走 +suggestion） |
+rsvp |
回复日程（接受/拒绝/待定） |
+join-event |
凭分享 token 加入日程（分享链接/二维码/分享卡片/RSVP 卡片） |
+suggestion |
根据非明确时间或一段时间范围，推荐多个可用时间块方案 |
+transfer |
把日程组织者转让给另一个用户或机器人；不可逆，需 --yes |
+list-attendees |
列出日程的参与人和会议室（支持按 --type 过滤：user / resource / chat / third_party） |
+get — 单日程详情
通过 calendar_id + event_id 获取单个日程详情。
What ships with it
13 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.
- references/lark-calendar-create.md 6.0 KB
- references/lark-calendar-join-event.md 2.0 KB
- references/lark-calendar-list-attendees.md 1.3 KB
- references/lark-calendar-meeting.md 1.6 KB
- references/lark-calendar-recurring.md 6.6 KB
- references/lark-calendar-room-find.md 8.2 KB
- references/lark-calendar-rsvp.md 1.1 KB
- references/lark-calendar-schedule-clear-time.md 2.8 KB
- references/lark-calendar-schedule-fuzzy-time.md 3.3 KB
- references/lark-calendar-schedule-meeting.md 6.1 KB
- references/lark-calendar-suggestion.md 6.9 KB
- references/lark-calendar-transfer.md 4.5 KB
- references/lark-calendar-update.md 7.8 KB
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 Changed · +28 lines 9a90ed21de5f
- 5d ago First seen · 216 lines · 92 tokens per session scan A 4a8816db9e10
lark-calendar is a skill published in the GitHub repository larksuite/cli (16,971 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 4,816 once invoked, about $0.0005 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…