clawd-feishu is a channel plugin that connects OpenClaw to Feishu/Lark, a collaboration and messaging platform. OpenClaw users use it to interact with the agent through Feishu or Lark.
Borrowing it
Nothing to install: this file belongs to m1heng/clawdbot-feishu. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/m1heng/clawdbot-feishu/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/m1heng/clawdbot-feishuWrote 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/m1heng/clawdbot-feishu/release)<a href="https://agentmods.dev/skills/m1heng/clawdbot-feishu/release"><img src="https://agentmods.dev/badge/skills/m1heng/clawdbot-feishu/release/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/m1heng/clawdbot-feishu/release"><img src="https://agentmods.dev/badge/skills/m1heng/clawdbot-feishu/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium MCP Rug Pull · line 4 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]
- medium MCP Rug Pull · line 37 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.00028 | $0.00641 |
| Opus 5 | $0.00014 | $0.00320 |
| Sonnet 5 | $0.00006 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
release 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 10d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Workflow
Publish a new version of @m1heng-clawd/feishu to npm and create a GitHub release.
Prerequisites
- Working tree is clean (all changes committed to
main) npm loginsession is active with publish access to@m1heng-clawdscopeghCLI is authenticated
Steps
1. Determine version bump
Check what changed since the last release:
# Find latest release tag
gh release list --limit 1
# Review commits and diff stat
git log <last-tag>..HEAD --oneline
git diff <last-tag>..HEAD --stat
Choose bump type: patch (bug fixes), minor (new features), or major (breaking changes).
2. Type check
npx tsc --noEmit
Do NOT proceed if type check fails.
3. Draft release notes
Review the full diff to write release notes:
git diff <last-tag>..HEAD
Create a GitHub release draft first:
gh release create v<new-version> --draft --title "v<new-version>" --target main --notes "<release notes markdown>"
4. Bump version in package.json
Edit package.json to update the "version" field to <new-version>.
5. Commit, tag, and push
git add package.json
git commit -m "chore: bump version to <new-version>"
git tag v<new-version>
git push && git push --tags
6. Publish to npm
npm publish
If auth fails, ask the user to run npm login first, then retry.
7. Publish GitHub release
gh release edit v<new-version> --draft=false
Release Notes Format
Follow the established format (see previous releases for reference):
## Features
- **Feature title** — Description. (#PR)
## Bug Fixes
- **Fix title** — Description. (#PR)
## Internal
- Internal change description.
Troubleshooting
npm publish 404 / auth error
npm login # re-authenticate
npm whoami # verify logged in
npm publish # retry
Tag already exists
If the tag was created but publish failed, delete and recreate after fixing:
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.
- 10d ago First seen · 120 lines · 28 tokens per session scan A 79484998c117
release is a skill published in the GitHub repository m1heng/clawdbot-feishu (4,245 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 641 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.