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/dropfan/claude-code-plugins/lark-calendarnpx skills add DropFan/claude-code-plugins --skill lark-calendargit clone --depth 1 https://github.com/DropFan/claude-code-pluginsWhat 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.03692 |
| Opus 5 | $0.00046 | $0.01846 |
| Sonnet 5 | $0.00018 | $0.00738 |
| Haiku 4.5 | $0.00009 | $0.00369 |
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 3d 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.
This is a copy
92% identical to lark-calendar — 86 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚙️ Cowork / Claude Desktop 执行环境说明（自动注入）
本技能依赖本地
lark-cli（@larksuite/cli，可用command -v lark-cli定位）及其~/.lark-cli登录态（应用密钥存于 macOS keychain）。在 Cowork 中运行任何
lark-cli命令时，必须在本地 macOS 上执行（使用 Desktop Commander 的start_process/interact_with_process，或其它本地 shell 工具），不要用隔离的 Linux 沙箱mcp__workspace__bash——沙箱里没有 lark-cli、也读不到 keychain。 执行前确保 npm 全局 bin 目录（npm prefix -g输出目录下的bin）在 PATH 中。（在 Claude Code 中可忽略本说明，lark-cli 在本机 shell 直接可用。）
calendar (v4)
开始前先读 ../lark-shared/SKILL.md（认证、权限处理）。
CRITICAL — 凡涉及预约日程/会议室、调整时间或查询/搜索会议室，第一步 MUST 读 references/lark-calendar-schedule-meeting.md。仅编辑字段（改标题/描述）或增删参会人（不涉及时间和会议室）时可跳过，直接读 references/lark-calendar-update.md。
身份
按日程归属选身份：
- 查看/管理登录用户本人的日程 →
--as user（默认，绝大多数场景）。 - 查看/管理 bot 自己创建/拥有的日程 →
--as bot
# 用户本人日程 → 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 |
+create |
创建日程并邀请参会人（ISO 8601 时间） |
+update |
更新既有日程字段，或独立增量添加/移除参会人和会议室 |
+freebusy |
查询用户主日历的忙闲信息和 RSVP 状态（纯查询场景；预约场景走 +suggestion） |
+room-find |
针对一个或多个明确的时间块查找可用会议室（无明确时间时禁止直接调用，需先走 +suggestion） |
+rsvp |
回复日程（接受/拒绝/待定） |
+suggestion |
根据非明确时间或一段时间范围，推荐多个可用时间块方案 |
+get — 单日程详情
通过 calendar_id + event_id 获取单个日程详情。
# calendar_id不传，默认primary
lark-cli calendar +get --calendar-id <calendar_id> --event-id <event_id>
日程描述统一使用 description 一个字段，按 Markdown 富文本处理。读取日程时 description 返回 Markdown 富文本（仅有纯文本描述时返回该纯文本）；创建/更新日程时也通过 --description 传入 Markdown。
What ships with it
10 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-meeting.md 1.6 KB
- references/lark-calendar-recurring.md 5.4 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.3 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-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.
- 3d ago First seen · 216 lines · 92 tokens per session scan A fec24a1f1c0d
lark-calendar is a skill published in the GitHub repository DropFan/claude-code-plugins (7 stars, last pushed 28d ago), licensed MIT. It adds 92 tokens to every session and 3,692 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to lark-calendar, differing in 86 lines, and is treated as a copy.
Other skills, from other repositories
auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog.
hook-template
Generate hook script from template. Use when adding a new hook, wiring a PreToolUse/PostToolUse/Stop/Notification hook, or scaffolding hook config for settings.json.
agent-check
Validate custom agent file format and structure. Use after creating or editing an agent, before committing agent changes, or when an agent fails to load.
skill-check
Validate skill/command file format and structure. Use after creating or editing a skill, before committing skill changes, or when a skill fails to load or trigger.
agent-template
Generate custom agent from template. Use when creating a new subagent from scratch, or scaffolding an agent file with correct frontmatter.
debugger
Systematic debugging method: 5-step root-cause analysis (capture, isolate, hypothesize, investigate, fix & verify) plus common bug-pattern reference. Use when errors, exceptions, test failures, or unexpected behavior appear. Loaded automatically by the debugger agent.