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/riba2534/feishu-cli/feishu-cli-worknpx skills add riba2534/feishu-cli --skill feishu-cli-workgit clone --depth 1 https://github.com/riba2534/feishu-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.00166 | $0.00625 |
| Opus 5 | $0.00083 | $0.00313 |
| Sonnet 5 | $0.00033 | $0.00125 |
| Haiku 4.5 | $0.00017 | $0.00063 |
Grade A, and why
feishu-cli-work 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.
What it actually says
飞书工作管理
加载工作流后，将其中 references/、scripts/、templates/、examples/ 相对路径按该
workflow.md 所在目录解析；执行脚本时使用解析后的实际路径，不要依赖当前 shell 目录。
路由
| 意图 | 读取文件 |
|---|---|
| 日历 CRUD、agenda、忙闲、智能时段、会议室、RSVP | references/workflows/calendar/workflow.md |
| 任务、子任务、成员、提醒、评论、附件、任务清单 | references/workflows/task/workflow.md |
| 审批定义、实例、任务、抄送和审批动作 | references/workflows/approval/workflow.md |
| 打卡任务和考勤统计 | references/workflows/attendance/workflow.md |
| OKR 周期、进展记录、创建 O/KR 与量化指标（api 透传） | references/workflows/okr/workflow.md |
执行规则
- 创建、修改、删除、审批通过/拒绝等操作会影响他人，执行前展示目标和关键参数。
task my、task search、全部审批命令（approval get/instance get|initiated|create|cancel|cc/task query|approve|reject|transfer）和calendar rsvp必须使用 User Token；其他命令按各工作流说明选择身份。- 时间统一使用带时区的 RFC3339；不要把全天事件和具体时段混用。
- 任务清单添加/移除任务使用
task-add/task-remove，不存在add-task/remove-task。
What ships with it
9 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.
- evals/evals.json 2.7 KB
- references/workflows/approval/references/form-control-values.md 4.5 KB
- references/workflows/approval/workflow.md 12 KB
- references/workflows/attendance/workflow.md 8.2 KB
- references/workflows/calendar/references/basic-commands.md 4.5 KB
- references/workflows/calendar/workflow.md 16 KB
- references/workflows/okr/workflow.md 15 KB
- references/workflows/task/references/commands.md 3.7 KB
- references/workflows/task/workflow.md 1.9 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 · 36 lines · 166 tokens per session scan A aace58cdd051
feishu-cli-work is a skill published in the GitHub repository riba2534/feishu-cli (1,378 stars, last pushed 5d ago), licensed MIT. It adds 166 tokens to every session and 625 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…