agentmods.dev

configure

configure is a skill for Claude Code from Agentchengfeng/claude-channel-feishu. It costs 61 tokens per session (1,040 once invoked), scanned B, original, Apache-2.0.

A command for configuring Feishu, a workplace messaging platform also known as Lark, for use as a communication channel.

In plain words
What is it for?
Use it to save Feishu app credentials, choose the China or international service, review direct-message and group-message routing, and check channel status.
Why use it?
It keeps the channel's app credentials and message-access rules in one place, making it clearer who can contact the system.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Part of the feishu plugin — 2 skills, 1 MCP server shipped together

not rated 6repo 3mo ago B scan 61 tokens original Apache-2.0

Good fit Use it to save Feishu app credentials, choose the China or international service, review direct-message and group-message routing, and check channel status.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/agentchengfeng/claude-channel-feishu/configure
View source ↗ Agentchengfeng/claude-channel-feishu
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.

Any agent
npx skills add Agentchengfeng/claude-channel-feishu --skill configure
Clone the repo
git clone --depth 1 https://github.com/Agentchengfeng/claude-channel-feishu

Made for: Claude Code.

Or install feishu, 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.

agentmods badge for configure

README.md
[![agentmods](https://agentmods.dev/badge/skills/agentchengfeng/claude-channel-feishu/configure/github.svg)](https://agentmods.dev/skills/agentchengfeng/claude-channel-feishu/configure)
Your own site
<a href="https://agentmods.dev/skills/agentchengfeng/claude-channel-feishu/configure"><img src="https://agentmods.dev/badge/skills/agentchengfeng/claude-channel-feishu/configure/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.

agentmods 80×15 button for configure

Your own site · 80×15
<a href="https://agentmods.dev/skills/agentchengfeng/claude-channel-feishu/configure"><img src="https://agentmods.dev/badge/skills/agentchengfeng/claude-channel-feishu/configure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,040 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.01040
Opus 5 $0.00030 $0.00520
Sonnet 5 $0.00012 $0.00208
Haiku 4.5 $0.00006 $0.00104

Measured 11d ago against content hash f30f997def7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 11d 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 STATE_DIR/.env`
skills/configure/SKILL.md · 107 lines

How it starts

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

/feishu:configure — Feishu Channel Setup

Writes the app credentials to STATE_DIR/.env and orients the user on routing mode and Feishu backend setup. The server reads credentials at boot and rereads routing config at runtime.

Arguments passed: $ARGUMENTS

Resolve STATE_DIR before you do anything:

  1. If $ARGUMENTS starts with --state-dir <path>, use that path and strip those two tokens before further parsing.
  2. Otherwise, if printenv FEISHU_STATE_DIR returns a non-empty path, use it.
  3. Otherwise, fall back to ~/.claude/channels/feishu.

Dispatch on arguments

No args — status and guidance

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

  1. Credentials — check STATE_DIR/.env for FEISHU_APP_ID and FEISHU_APP_SECRET. Show set/not-set; if set, show first 8 chars masked (cli_xxxx...).

  2. Domain — check for FEISHU_DOMAIN. Default is feishu (China). lark for international.

  3. Routing — read STATE_DIR/access.json (missing file = defaults: open DMs, group mention-gated). Show:

    • DMs are open from any sender
    • Group messages require an @ mention unless that group has requireMention:false
    • Permission-card recipients from allowFrom

  4. What next — end with a concrete next step based on state:

    • No credentials → guide them through Feishu backend setup (see below)
    • Credentials set → "Ready. DM your bot or @ it in a group to reach the assistant."

Feishu backend setup guide

When the user needs to create a Feishu app, walk them through:

  1. Go to Feishu Open Platform → Create Custom App
  2. In Credentials & Basic Info: copy App ID and App Secret
  3. In Bot section: enable Bot capability
  4. In Permissions & Scopes: add these scopes:
    • im:message — send and receive messages
    • im:message:send_as_bot — send messages as bot
    • im:resource — download message resources (images/files)
    • im:message.reactions:write — add emoji reactions (optional)
  5. In Event Subscriptions:
    • Choose WebSocket mode (长连接)
    • Add event: im.message.receive_v1
    • Add event: card.action.trigger (for permission buttons)
  6. Create a version and publish → wait for admin approval

Read the full file on GitHub · 107 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.

  1. 11d ago First seen · 107 lines · 61 tokens per session scan B f30f997def7c

Subscribe to this mod's changes

configure is a skill published in the GitHub repository Agentchengfeng/claude-channel-feishu (6 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,040 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens