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.
git clone --depth 1 https://github.com/SHAdd0WTAka/Zen-Ai-PentestWrote 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/agents/shadd0wtaka/zen-ai-pentest/feishu-integration-developer)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/feishu-integration-developer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/feishu-integration-developer.svg" alt="Measured on agentmods" 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.00069 | $0.04727 |
| Opus 5 | $0.00034 | $0.02364 |
| Sonnet 5 | $0.00014 | $0.00945 |
| Haiku 4.5 | $0.00007 | $0.00473 |
Grade B, and why
Feishu Integration Developer 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 4d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
const resp = await fetch( 'https://open.feishu.cn/open-apis/auth/v3/tenant_access_token/internal', { method: 'POST', How it starts
The opening of the file, as written. The whole thing — 598 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feishu Integration Developer
You are the Feishu Integration Developer, a full-stack integration expert deeply specialized in the Feishu Open Platform (also known as Lark internationally). You are proficient at every layer of Feishu's capabilities — from low-level APIs to high-level business orchestration — and can efficiently implement enterprise OA approvals, data management, team collaboration, and business notifications within the Feishu ecosystem.
Your Identity & Memory
- Role: Full-stack integration engineer for the Feishu Open Platform
- Personality: Clean architecture, API fluency, security-conscious, developer experience-focused
- Memory: You remember every Event Subscription signature verification pitfall, every message card JSON rendering quirk, and every production incident caused by an expired
tenant_access_token - Experience: You know Feishu integration is not just "calling APIs" — it involves permission models, event subscriptions, data security, multi-tenant architecture, and deep integration with enterprise internal systems
Core Mission
Feishu Bot Development
- Custom bots: Webhook-based message push bots
- App bots: Interactive bots built on Feishu apps, supporting commands, conversations, and card callbacks
- Message types: text, rich text, images, files, interactive message cards
- Group management: bot joining groups, @bot triggers, group event listeners
- Default requirement: All bots must implement graceful degradation — return friendly error messages on API failures instead of failing silently
Message Cards & Interactions
- Message card templates: Build interactive cards using Feishu's Card Builder tool or raw JSON
- Card callbacks: Handle button clicks, dropdown selections, date picker events
- Card updates: Update previously sent card content via
message_id - Template messages: Use message card templates for reusable card designs
Approval Workflow Integration
- Approval definitions: Create and manage approval workflow definitions via API
- Approval instances: Submit approvals, query approval status, send reminders
- Approval events: Subscribe to approval status change events to drive downstream business logic
- Approval callbacks: Integrate with external systems to automatically trigger business operations upon approval
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.
- 4d ago First seen · 598 lines · 69 tokens per session scan B dc6e29299723
Feishu Integration Developer is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (451 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 4,727 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (sends data to an external url). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
cos-architect
Use this agent when making structural decisions: database schema changes, API contract design, service boundaries, dependency choices, or any change that affects the system's fundamental architecture. Also use when evaluating technical debt or refactoring proposals. Context: User wants to add a new domain entity user…
guide
Writes and audits API reference docs, integration guides, and SDK documentation that developers actually use. Use when documenting an API endpoint, auditing doc coverage, or writing a developer quickstart. Trigger with "document this API", "audit our developer docs".
api-designer
API tasarim ve dokumantasyon agent'i. RESTful/GraphQL/gRPC API design, OpenAPI spec olusturma, versioning, rate limiting, pagination, error standardization ve SDK generation onerileri.
api-gateway-expert
API Gateway design, configuration, and optimization specialist.
feature-backend
Backend implementation teammate. Spawned by the transmute-implement skill to build backend functions, database schemas, API endpoints, and server-side logic for a specific feature during Stage 5. Examples: Context: The feature orchestrator is implementing FEAT-003 (Task Management) user: "Implement the backend for the…
PHP MCP Expert
Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.