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 fanfan-de/anybox --skill feishu-cligit clone --depth 1 https://github.com/fanfan-de/anyboxWrote 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/fanfan-de/anybox/feishu-cli)<a href="https://agentmods.dev/skills/fanfan-de/anybox/feishu-cli"><img src="https://agentmods.dev/badge/skills/fanfan-de/anybox/feishu-cli/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/fanfan-de/anybox/feishu-cli"><img src="https://agentmods.dev/badge/skills/fanfan-de/anybox/feishu-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 14 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Excessive Agency · line 14 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium MCP Rug Pull · line 29 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00058 | $0.01096 |
| Opus 5 | $0.00029 | $0.00548 |
| Sonnet 5 | $0.00012 | $0.00219 |
| Haiku 4.5 | $0.00006 | $0.00110 |
Grade A, and why
feishu-cli 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feishu CLI
Use this skill when the user asks to use Feishu, Lark, Feishu CLI, Lark CLI, or lark-cli from the agent shell. This is a CLI-first workflow, not an MCP workflow. Use shell commands to call lark-cli directly.
Operating Model
- Prefer
lark-clifor Feishu/Lark work instead of direct HTTP calls when this skill is active. - Treat
lark-clias the owner of app configuration, OAuth login, scopes, user/bot identity selection, and local credential storage. - Do not ask the user for access tokens, refresh tokens, app secrets, or cookies. Do not print or save secrets.
- Use
--format jsonfor read commands whenever supported so results are machine-readable. - Keep commands narrow and explicit. Avoid raw OpenAPI calls unless a shortcut or service command cannot do the job.
Setup Checks
First check whether the CLI is available:
lark-cli --version
If it is missing, tell the user it needs to be installed, then use the official installer when the user wants you to proceed:
npx @larksuite/cli@latest install
After installation, initialize app configuration if needed:
lark-cli config init --new
Then check login state:
lark-cli auth status
If not logged in, start login with recommended scopes:
lark-cli auth login --recommend
For agent-driven browser handoff, use non-blocking login when appropriate and relay only the authorization URL or next safe instruction to the user:
lark-cli auth login --recommend --no-wait
Safety Rules
- Before sending messages, modifying documents, updating calendars, changing records, approving requests, deleting anything, or calling raw write APIs, get explicit user confirmation unless the user has already clearly asked for that exact action.
- For write commands that support it, run
--dry-runfirst and summarize the intended change before executing the real command. - Do not add the Feishu/Lark bot to public or broad group chats as part of setup. If group access is needed, ask the user to handle membership deliberately.
- Never run broad destructive commands such as bulk delete, recursive permission changes, or mass updates unless the user explicitly scopes the target set.
- When a command fails for missing scope or permission, report the missing capability and use
lark-cli auth checkorlark-cli auth loginwith a narrower domain or scope instead of retrying blindly.
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.
- 9d ago First seen · 116 lines · 58 tokens per session scan A 3e3607793987
feishu-cli is a skill published in the GitHub repository fanfan-de/anybox (57 stars, last pushed 29d ago), licensed MIT. It adds 58 tokens to every session and 1,096 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.