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.
npx skills add nongjun/feishu-cursor-claw --skill customer-filtergit clone --depth 1 https://github.com/nongjun/feishu-cursor-clawWrote 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/nongjun/feishu-cursor-claw/customer-filter)<a href="https://agentmods.dev/skills/nongjun/feishu-cursor-claw/customer-filter"><img src="https://agentmods.dev/badge/skills/nongjun/feishu-cursor-claw/customer-filter.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.00065 | $0.00662 |
| Opus 5 | $0.00032 | $0.00331 |
| Sonnet 5 | $0.00013 | $0.00132 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
customer-filter 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 8d 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.
What it actually says
客户筛选器
组件分层
| 层级 | 位置 | 特点 |
|---|---|---|
| 基础组件 | shared_frontend/components/CustomerFilterBase.vue | 通用条件框架 |
| 完整组件 | 撩回搭子/前端服务/components/customer-filter/CustomerFilter.vue | 含员工选择、模板、手动勾选 |
支持的筛选条件
| 条件 | 基础组件 | 完整组件 |
|---|---|---|
| 沉默天数 | Y | Y |
| 客户标签（插槽） | Y | Y |
| 最后互动时间 | Y | Y |
| 客户来源（插槽） | Y | Y |
| 归属员工 | - | Y（必选项） |
| 互动次数 | - | Y |
| 所属企业（B2B） | - | Y |
| 跟进状态 | - | Y |
| 手动勾选客户 | - | Y（V5.2） |
| 上传名单 | - | Y（V5.2） |
完整组件暴露方法
| 方法 | 用途 |
|---|---|
| getFilterData() | 获取当前筛选条件 |
| getPreviewCount() | 获取预览数量 |
| validate() | 验证筛选条件 |
| getSelectedCustomers() | 获取已选客户列表 |
后端服务（CustomerFilterService）
位于 shared_backend/services/customer_filter_service.py
| 方法 | 用途 |
|---|---|
| build_query() | 构建 SQL 查询 |
| preview() | 预览筛选结果（数量+样本） |
| list_customers() | 分页获取客户列表 |
| get_customer_ids() | 获取 ID 列表 |
| get_count() | 仅获取数量 |
API 路径
- POST /liaohui/customer-filter/preview
- POST /liaohui/customer-filter/list
- GET /liaohui/customer-filter/templates
- POST /liaohui/customer-filter/match-by-phone
- GET /liaohui/customer-filter/search
SOP：集成客户筛选
- 简单场景：直接用 CustomerFilterBase + 插槽
- 完整场景：引入撩回搭子的 CustomerFilter 组件
- 后端：实例化 CustomerFilterService(db, current_user)，调用对应方法
- 新增筛选条件：前端加条件 UI，后端在 build_query() 中扩展
参考文件
- 公共模块/shared_frontend/components/CustomerFilterBase.vue
- 公共模块/shared_backend/services/customer_filter_service.py
- 撩回搭子/前端服务/src/components/customer-filter/
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.
- 8d ago First seen · 71 lines · 65 tokens per session scan A cdd890db2995
customer-filter is a skill published in the GitHub repository nongjun/feishu-cursor-claw (14 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 662 once invoked, about $0.0003 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
metabot-team
Use for the MetaBot Agent Teams CLI: create and inspect durable Teams, spawn teammates, exchange messages, and manage Tasks and Runs across Sessions.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
firebase-cloud-functions
Use when calling callable functions (httpsCallable), passing data to server-side logic, handling function errors/timeouts, configuring regions, or testing with the Emulator Suite.
audit-payment-system
Read-only audit for payment/money-movement systems, scope-gated so a Stripe-Checkout site and an in-house ledger each see only relevant findings. Use when "audit payment system", "double charge / idempotency", "ledger / reconciliation", "webhook / 3DS / PCI". Mobile IAP → audit-monetization-iap.
audit-ux
Per-page UX audit using NN/g heuristics, Intuit microcopy, and Google HEART. Use when evaluating usability, auditing microcopy, checking UX heuristics, or assessing cognitive load. Cross-page flows/IA → audit-ux-journeys. Layout/breakpoints → audit-responsive. Empty/error states → audit-ui-states.
enhance-web-web3d
Add purposeful 3D/WebGL and scroll choreography to an existing site with Three.js/R3F, GSAP, or Motion. Use when "add 3D", "WebGL hero", "React Three Fiber", or "scroll-driven 3D". General UI polish → enhance-web-ui. Motion without 3D → enhance-motion.