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-markdownnpx skills add DropFan/claude-code-plugins --skill lark-markdowngit 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.00073 | $0.01572 |
| Opus 5 | $0.00036 | $0.00786 |
| Sonnet 5 | $0.00015 | $0.00314 |
| Haiku 4.5 | $0.00007 | $0.00157 |
Grade A, and why
lark-markdown 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.
This is a copy
86% identical to lark-markdown — 13 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 — 82 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 直接可用。）
markdown (v1)
CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md，其中包含认证、权限处理
快速决策
-
身份：Markdown 文件通常属于用户云空间资源，优先使用
--as user。如为自动化场景，或应用已创建并持有目标文件权限，可按场景使用--as bot。首次以user身份访问前执行lark-cli auth login -
markdown +create/+overwrite失败时，先判断是不是身份和权限问题：bot更常见的是 app scope 或目标目录 ACL，user更常见的是用户授权或用户 ACL；不要不加判断地来回切身份重试。 -
用户要上传、创建一个原生
.md文件，使用lark-cli markdown +create -
用户要比较原生
.md文件的历史版本差异，或比较远端 Markdown 与本地草稿，使用lark-cli markdown +diff -
用户要读取 Drive 里某个
.md文件内容，使用lark-cli markdown +fetch -
用户要对 Markdown 文件做局部文本替换 / 正则替换，优先使用
lark-cli markdown +patch -
用户要覆盖更新 Drive 里某个
.md文件内容，使用lark-cli markdown +overwrite -
用户要先拿 Markdown 文件的历史版本号，再做比较/下载/回滚，先用
lark-drive的lark-cli drive +version-history -
用户要把本地 Markdown 导入成在线新版文档（docx），不要用本 skill，改用
lark-drive的lark-cli drive +import --type docx -
用户要对 Markdown 文件做rename / move / delete / 搜索 / 权限 / 评论等云空间（云盘/云存储）操作，不要留在本 skill，切到
lark-drive -
markdown +create/+overwrite命中missing scope、permission denied、not found、quota_exceeded、version limit时，默认停止重试并按报错 hint 处理；只有rate_limit、server_error或临时网络错误才做有限退避重试。 -
markdown +create的目标参数不要猜：Drive 文件夹用--folder-token，Wiki 节点用--wiki-token。如果用户给的是 URL，可以直接传完整 URL；CLI 会归一成 token。不要把 doc/sheet/wiki URL 放进--folder-token试错。
核心边界
- 本 skill 处理的是 Drive 中作为普通文件存储的 Markdown，不是 docx 文档
--name和本地--file文件名都必须显式带.md后缀；不满足时 shortcut 会直接报错--content支持：- 直接传字符串
@file从本地文件读取内容-从 stdin 读取内容
markdown +patch的内部语义是：先完整下载 Markdown，再本地替换，再整文件覆盖上传markdown +patch不是服务端原子 patch；它是 CLI 侧编排出来的局部更新能力markdown +patch当前只支持单组--pattern/--contentmarkdown +patch替换后的最终内容不能为空；CLI 会拒绝上传空文件，因为 Drive 不支持零字节 Markdown，且空文件通常是误操作--file只接受本地.md文件路径
What ships with it
5 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.
- 2d ago First seen · 82 lines · 73 tokens per session scan A a7eb7348f4b6
lark-markdown is a skill published in the GitHub repository DropFan/claude-code-plugins (7 stars, last pushed 27d ago), licensed MIT. It adds 73 tokens to every session and 1,572 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to lark-markdown, differing in 13 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.
session-relay
Continue real repository work between Claude Code, Codex CLI, and Grok Build with a privacy-bounded, drift-aware handoff packet. Use for cross-vendor takeover, context-limit checkpoints, multi-hop Claude→Codex→Grok relays, or receiving an existing Director packet. Use native resume commands for same-CLI history; never…
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.
skill-template
Generate custom skill/command from template. Use when creating a new skill or slash command from scratch, or scaffolding a skill file with correct frontmatter.