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 chat-viewergit 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/chat-viewer)<a href="https://agentmods.dev/skills/nongjun/feishu-cursor-claw/chat-viewer"><img src="https://agentmods.dev/badge/skills/nongjun/feishu-cursor-claw/chat-viewer.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.00059 | $0.00563 |
| Opus 5 | $0.00030 | $0.00282 |
| Sonnet 5 | $0.00012 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
chat-viewer 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
聊天记录查看器
架构
- 后端统一：会话存档模块的 ChatService 处理消息同步、解密、媒体下载
- 前端分散：各业务模块按需实现查看组件
后端核心服务（ChatService）
| 方法 | 用途 |
|---|---|
| sync_messages_from_wecom() | 从企微批量同步+解密+入库 |
| get_customer_messages() | 获取指定客户/群聊的聊天记录 |
| _download_media_if_needed() | 自动下载媒体文件 |
| _recognize_voice_message() | 语音转文字（腾讯云 ASR） |
支持的消息类型
| msgtype | 渲染方式 |
|---|---|
| text | 文字气泡 |
| image | 缩略图 + 点击放大 |
| voice | 播放按钮 + 转文字 |
| video | video 播放器 |
| file | 文件图标 + 下载链接 |
| emotion | 表情图片 |
| link | 链接卡片 |
| weapp | 小程序链接 |
前端组件位置
| 模块 | 组件 | 用途 |
|---|---|---|
| 撩回搭子 | ChatPreview.vue | 客户聊天预览 |
| 联系人侧边栏 | ChatDetailDrawer.vue | 完整聊天详情 |
| 联系人侧边栏 | ChatSummaryByUserCard.vue | 聊天摘要卡片 |
API 端点
| 端点 | 方法 | 说明 |
|---|---|---|
| /api/archive/messages | GET | 获取聊天记录（分页） |
| /api/media/{msgid} | GET | 获取媒体文件 |
重点关注
- 语音转码依赖 FFmpeg（AMR → MP3），Docker 中需安装
- 语音识别使用腾讯云 ASR，需配置 SecretId/SecretKey
- 消息同步后会触发下游事件（撩回搭子通知、AI标签等）
- 单聊查询需同时查 from_userid 和 external_userid 双向
参考文件
- 会话存档/后端服务/app/services/chat_service.py
- 联系人/前端-侧边栏/src/components/ChatDetailDrawer.vue
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 · 61 lines · 59 tokens per session scan A 88eae828408a
chat-viewer is a skill published in the GitHub repository nongjun/feishu-cursor-claw (14 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 563 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
audit-fe-api
Audit frontend API calls against backend implementation for contract alignment and network shape. Use when "API audit", "FE-BE contract", or "review frontend API integration". Live 4xx/5xx reproduction → debug-fe-be-integration.
backend-realtime
Implement real-time features using WebSockets, Supabase Realtime, Server-Sent Events, and live data. Use when user wants "real-time", "live updates", "WebSocket", "notifications", "chat", "collaborative", "presence", "live data", or "instant sync".
react-server-components
Implements React Server Components (RSC) patterns with Next.js App Router including data fetching, streaming, selective hydration, and server/client composition. Use when users request "server components", "RSC", "Next.js app router", "server-side rendering", or "streaming".
firebase-auth
Use when setting up auth, managing auth state, implementing email/password or social sign-in, handling auth errors, or managing users.
architecture-feature-first
Use when creating a feature, designing folder structure, adding repositories/services/view models, wiring dependency injection, or deciding which layer owns logic.
create-handler
Create a new API handler following the handler pattern. Use when the user asks to create an endpoint, handler, or route.