Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ZW471/claude-feishu-calendar/plugin install feishu-calendarWrote 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/zw471/claude-feishu-calendar/feishu-calendar)<a href="https://agentmods.dev/skills/zw471/claude-feishu-calendar/feishu-calendar"><img src="https://agentmods.dev/badge/skills/zw471/claude-feishu-calendar/feishu-calendar/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/zw471/claude-feishu-calendar/feishu-calendar"><img src="https://agentmods.dev/badge/skills/zw471/claude-feishu-calendar/feishu-calendar.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.00119 | $0.00979 |
| Opus 5 | $0.00060 | $0.00490 |
| Sonnet 5 | $0.00024 | $0.00196 |
| Haiku 4.5 | $0.00012 | $0.00098 |
Grade A, and why
feishu-calendar 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feishu Calendar Skill
Manage Feishu (Lark) calendar events via the Open Platform Calendar API v4.
Execution Modes
This skill works in two environments. Detect which one you are in and follow the matching workflow.
Claude Code (has internet access)
Run the Python scripts directly via Bash. No need to ask the user to run anything.
# Write config.json, then execute run.py directly
cd ${CLAUDE_PLUGIN_ROOT}/skills/feishu-calendar/scripts && python run.py
You can also run individual tools directly:
cd ${CLAUDE_PLUGIN_ROOT}/skills/feishu-calendar/scripts && python -c "
import sys; sys.path.insert(0, 'tools')
from list_events import run
run({'calendar_id': '[email protected]', 'days': 7})
"
Or use run.py with a config.json you write — same result, just write config.json then python run.py.
Cowork (sandboxed, no internet)
Cowork cannot call the Feishu API. Use the config.json → run.py → user workflow:
- Write
config.jsonin thescripts/directory. - Ask the user to run:
python run.pyfrom thescripts/directory. - Read the output the user pastes back, or read
output.json.
Setup
On first use, check that .env exists in scripts/. If not, ask the user for their Feishu App ID and App Secret, then create scripts/.env:
FEISHU_APP_ID=<their_app_id>
FEISHU_APP_SECRET=<their_app_secret>
FEISHU_BASE_URL=https://open.feishu.cn
See INSTALL.md at the plugin root for detailed setup instructions.
Quick Reference
| What to do | Tool name | Key params |
|---|---|---|
| List calendars | list_calendars |
(none) |
| List events in a range | list_events |
calendar_id, start, end, days |
| Get event details | get_event |
calendar_id, event_id |
| Create events | create_events |
calendar_id, events[] |
| Update an event | update_event |
calendar_id, event_id, + fields |
| Delete events | delete_events |
calendar_id, event_ids[] |
| Add/list attendees | manage_attendees |
calendar_id, event_id, action, attendees[] |
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/agent-guide.md 10 KB
- references/calendars.md 366 B
- scripts/config.json 153 B
- scripts/run.py 3.4 KB runs code
- scripts/tools/__init__.py 0 B runs code
- scripts/tools/api_client.py 4.8 KB runs code
- scripts/tools/create_events.py 4.0 KB runs code
- scripts/tools/delete_events.py 1.8 KB runs code
- scripts/tools/get_event.py 1.2 KB runs code
- scripts/tools/list_calendars.py 872 B runs code
- scripts/tools/list_events.py 2.4 KB runs code
- scripts/tools/manage_attendees.py 3.0 KB runs code
- scripts/tools/update_event.py 2.3 KB runs code
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 · 114 lines · 119 tokens per session scan A eff0ad9906cf
feishu-calendar is a skill published in the GitHub repository ZW471/claude-feishu-calendar (6 stars, last pushed 5mo ago), licensed MIT. It adds 119 tokens to every session and 979 once invoked, about $0.0006 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.