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 skills add YeSongYun/openclaw-cn --skill feishu-permgit clone --depth 1 https://github.com/YeSongYun/openclaw-cnWrote 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/yesongyun/openclaw-cn/feishu-perm)<a href="https://agentmods.dev/skills/yesongyun/openclaw-cn/feishu-perm"><img src="https://agentmods.dev/badge/skills/yesongyun/openclaw-cn/feishu-perm/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/yesongyun/openclaw-cn/feishu-perm"><img src="https://agentmods.dev/badge/skills/yesongyun/openclaw-cn/feishu-perm.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00024 | $0.00638 |
| Opus 5 | $0.00012 | $0.00319 |
| Sonnet 5 | $0.00005 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
feishu-perm 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 12d 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
100% identical to feishu-perm — 81 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feishu Permission Tool
Single tool feishu_perm for managing file/document permissions.
Actions
List Collaborators
{ "action": "list", "token": "ABC123", "type": "docx" }
Returns: members with member_type, member_id, perm, name.
Add Collaborator
{
"action": "add",
"token": "ABC123",
"type": "docx",
"member_type": "email",
"member_id": "[email protected]",
"perm": "edit"
}
Remove Collaborator
{
"action": "remove",
"token": "ABC123",
"type": "docx",
"member_type": "email",
"member_id": "[email protected]"
}
Token Types
| Type | Description |
|---|---|
doc |
Old format document |
docx |
New format document |
sheet |
Spreadsheet |
bitable |
Multi-dimensional table |
folder |
Folder |
file |
Uploaded file |
wiki |
Wiki node |
mindnote |
Mind map |
Member Types
| Type | Description |
|---|---|
email |
Email address |
openid |
User open_id |
userid |
User user_id |
unionid |
User union_id |
openchat |
Group chat open_id |
opendepartmentid |
Department open_id |
Permission Levels
| Perm | Description |
|---|---|
view |
View only |
edit |
Can edit |
full_access |
Full access (can manage permissions) |
Examples
Share document with email:
{
"action": "add",
"token": "doxcnXXX",
"type": "docx",
"member_type": "email",
"member_id": "[email protected]",
"perm": "edit"
}
Share folder with group:
{
"action": "add",
"token": "fldcnXXX",
"type": "folder",
"member_type": "openchat",
"member_id": "oc_xxx",
"perm": "view"
}
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.
- 12d ago First seen · 120 lines · 24 tokens per session scan A db64b7c5ccb4
feishu-perm is a skill published in the GitHub repository YeSongYun/openclaw-cn (56 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 638 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to feishu-perm, differing in 81 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…