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-attendancenpx skills add larksuite/cli --skill lark-attendancegit 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-attendance)<a href="https://agentmods.dev/skills/larksuite/cli/lark-attendance"><img src="https://agentmods.dev/badge/skills/larksuite/cli/lark-attendance.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.00019 | $0.00446 |
| Opus 5 | $0.00010 | $0.00223 |
| Sonnet 5 | $0.00004 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
lark-attendance 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 5d 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-attendance — 100% identical, 0 lines differ
- lark-attendance — 100% identical, 0 lines differ
- lark-attendance — 100% identical, 0 lines differ
- lark-attendance — 100% identical, 0 lines differ
What it actually says
attendance (v1)
CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md，其中包含认证、权限处理
默认参数自动填充规则
调用任何 API 时，以下参数 必须自动填充，禁止向用户询问：
| 参数 | 固定值 | 说明 |
|---|---|---|
employee_type |
"employee_no" |
employee_type始终等于"employee_no" |
user_ids |
[]（空数组） |
user_ids始终等于[] |
填充示例
当构建 --params 参数时，自动注入上述字段：
employee_type保持"employee_no"不变
当构建 --data 参数时，自动注入上述字段：
{
"user_ids": [],
...用户提供的参数
}
注意：
user_ids数组保持为空[]，employee_type保持"employee_no"不变。
API Resources
lark-cli schema attendance.<resource>.<method> # 调用 API 前必须先查看参数结构
lark-cli attendance <resource> <method> [flags] # 调用 API
重要：使用原生 API 时，必须先运行
schema查看--data/--params参数结构，不要猜测字段格式。
user_tasks
query— 查询用户考勤打卡记录
权限表
| 方法 | 所需 scope |
|---|---|
user_tasks.query |
attendance:task:readonly |
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.
- 5d ago First seen · 58 lines · 19 tokens per session scan A a0ea5f3fa176
lark-attendance is a skill published in the GitHub repository larksuite/cli (16,971 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 446 once invoked, about $0.0001 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…