A setup skill for connecting the Feishu workplace-messaging app to Claude Code. It stores Feishu app credentials and explains the current access policy, including pairing and approved senders.

Use it to configure Feishu credentials, inspect channel status, review allowed users and pending pairings, and approve a pairing code.

It shows whether credentials and access settings are ready and tells the user what action is needed next. This reduces guesswork when configuring or checking the channel.

configure — Skill for Claude Code by AnInteger: A setup skill for connecting the Feishu workplace-messaging app…

Install

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.

agentmods

npx agentmods add skills/aninteger/claude-channel-feishu/configure

Any agent

npx skills add AnInteger/claude-channel-feishu --skill configure

Clone the repo

git clone --depth 1 https://github.com/AnInteger/claude-channel-feishu

Made for: Claude Code.

Or install feishu-unofficial, the plugin that ships this one along with the rest of its 2 skills, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aninteger/claude-channel-feishu/configure.svg)](https://agentmods.dev/skills/aninteger/claude-channel-feishu/configure)

Your own site

<a href="https://agentmods.dev/skills/aninteger/claude-channel-feishu/configure"><img src="https://agentmods.dev/badge/skills/aninteger/claude-channel-feishu/configure.svg" alt="Measured on agentmods" height="20"></a>

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,101 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00057	$0.01101
Opus 5	$0.00028	$0.00550
Sonnet 5	$0.00011	$0.00220
Haiku 4.5	$0.00006	$0.00110

Measured 6d ago against content hash cd9f33373017, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade B, and why

configure scanned grade B with 1 finding 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 6d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

4. `chmod 600 ~/.claude/channels/feishu/.env` — credentials are secrets.

skills/configure/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/feishu-unofficial:configure — Feishu Channel Setup

Writes the Feishu app credentials to ~/.claude/channels/feishu/.env and orients the user on access policy. The server reads both files at boot.

Arguments passed: $ARGUMENTS

Dispatch on arguments

No args — status and guidance

Read both state files and give the user a complete picture:

Credentials — check ~/.claude/channels/feishu/.env for FEISHU_APP_ID and FEISHU_APP_SECRET. Show set/not-set; if set, show first 8 chars masked (cli_a936...).
Access — read ~/.claude/channels/feishu/access.json (missing file = defaults: dmPolicy: "pairing", empty allowlist). Show:
- DM policy and what it means in one line
- Allowed senders: count, and list display names or IDs
- Pending pairings: count, with codes and display names if any
What next — end with a concrete next step based on state:
- No credentials → "Run /feishu-unofficial:configure <app_id> <app_secret> with the credentials from Feishu Admin Console."
- Credentials set, policy is pairing, nobody allowed → "DM your bot on Feishu. It replies with a code; approve with /feishu-unofficial:access pair <code>."
- Credentials set, someone allowed → "Ready. DM your bot to reach the assistant."

Push toward lockdown — always. The goal for every setup is allowlist with a defined list. pairing is not a policy to stay on; it's a temporary way to capture Feishu user IDs you don't know. Once the IDs are in, pairing has done its job and should be turned off.

Drive the conversation this way:

Read the allowlist. Tell the user who's in it.
Ask: "Is that everyone who should reach you through this bot?"
If yes and policy is still pairing → "Good. Let's lock it down so nobody else can trigger pairing codes:" and offer to run /feishu-unofficial:access policy allowlist. Do this proactively — don't wait to be asked.
If no, people are missing → "Have them DM the bot; you'll approve each with /feishu-unofficial:access pair <code>. Run this skill again once everyone's in and we'll lock it."
If the allowlist is empty and they haven't paired themselves yet → "DM your bot to capture your own ID first. Then we'll add anyone else and lock it down."
If policy is already allowlist → confirm this is the locked state. If they need to add someone: "They'll need to give you their Open ID (have them check their profile or message you their ID), or you can briefly flip to pairing: /feishu-unofficial:access policy pairing → they DM → you pair → flip back."

Read the full file on GitHub · 100 lines

Changes

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.

6d ago First seen · 100 lines · 57 tokens per session scan B cd9f33373017

Subscribe to this mod's changes

configure is a skill published in the GitHub repository AnInteger/claude-channel-feishu (6 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,101 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Productivity

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…

nexu-io/open-design · 117 tokens

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…

danielmiessler/LifeOS · 196 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

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.

pinchtab/pinchtab · 52 tokens