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 agentmods add skills/vibeinging/yiyi/bot_setupnpx skills add vibeinging/YiYi --skill bot_setupgit clone --depth 1 https://github.com/vibeinging/YiYiWrote 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/vibeinging/yiyi/bot_setup)<a href="https://agentmods.dev/skills/vibeinging/yiyi/bot_setup"><img src="https://agentmods.dev/badge/skills/vibeinging/yiyi/bot_setup.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 | $0.00068 | $0.02039 |
| Opus 5 | $0.00034 | $0.01019 |
| Sonnet 5 | $0.00014 | $0.00408 |
| Haiku 4.5 | $0.00007 | $0.00204 |
Grade A, and why
bot_setup 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 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.
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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bot 配置引导技能
当用户说「帮我添加飞书机器人」「配置 Discord bot」「连接 Telegram」等时,使用此技能引导用户完成整个配置流程。
核心流程
- 确认平台 — 询问用户要配置哪个平台
- 打开浏览器 — 用
browser_use(headed=true)打开对应平台的开发者控制台 - 引导操作 — 使用
ai_snapshot+act辅助用户在页面上操作 - 获取凭据 — 从页面提取 App ID、Secret 等信息
- 创建 Bot — 调用
manage_bot的 create action 完成创建 - 测试连接 — 启动 Bot 并发送测试消息
各平台详细配置步骤
飞书 (Feishu)
所需凭据: app_id, app_secret, webhook_url
步骤 1: 创建应用
- 打开 https://open.feishu.cn/app (国际版: https://open.larksuite.com/app)
- 如果用户未登录,提示用户登录飞书账号
- 点击「创建企业自建应用」
- 填写应用名称和描述
步骤 2: 获取凭据
- 进入应用 → 「凭证与基础信息」页面
- 复制 App ID(格式:
cli_xxxxxxxx) - 复制 App Secret
步骤 3: 启用机器人能力
- 进入「应用能力 > 机器人」
- 开启机器人功能
步骤 4: 配置权限
- 进入「权限管理」
- 搜索并开通以下权限:
im:message— 获取与发送消息im:message:send_as_bot— 以机器人身份发送消息im:chat:readonly— 获取群组信息contact:user.id:readonly— 获取用户 ID
步骤 5: 配置事件订阅
- 进入「事件订阅」
- 选择「使用长连接接收事件」(推荐,无需公网 URL)
- 或设置请求地址:
http://<你的IP>:9090/webhook/feishu
- 或设置请求地址:
- 添加事件:
im.message.receive_v1(接收消息)
步骤 6: 发布应用
- 进入「版本管理与发布」
- 创建版本并提交审核
- 审核通过后即可使用
步骤 7: 在 YiYi 创建 Bot
{
"action": "create",
"platform": "feishu",
"name": "我的飞书机器人",
"config": {
"app_id": "cli_xxxxxxxx",
"app_secret": "从页面复制的密钥",
"webhook_url": "https://open.feishu.cn/open-apis/bot/v2/hook/xxxxx"
}
}
钉钉 (DingTalk)
所需凭据: webhook_url, secret
步骤 1: 创建机器人
- 打开 https://open-dev.dingtalk.com/
- 登录后进入「应用开发 > 机器人」
- 点击「创建机器人」
步骤 2: 获取 Webhook
- 在群设置中添加自定义机器人
- 安全设置选择「加签」,复制 Secret
- 复制 Webhook URL
步骤 3: 在 YiYi 创建 Bot
{
"action": "create",
"platform": "dingtalk",
"name": "我的钉钉机器人",
"config": {
"webhook_url": "https://oapi.dingtalk.com/robot/send?access_token=xxx",
"secret": "SECxxxxxxxx"
}
}
所需凭据: app_id, client_secret
步骤 1: 创建应用
- 打开 https://q.qq.com/
- 登录 QQ 开放平台
- 创建一个机器人应用
步骤 2: 获取凭据
- 在应用详情中复制 App ID 和 Client Secret
- 配置沙箱或正式环境的频道权限
步骤 3: 在 YiYi 创建 Bot
{
"action": "create",
"platform": "qq",
"name": "我的QQ机器人",
"config": {
"app_id": "你的AppID",
"client_secret": "你的ClientSecret"
}
}
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 · 270 lines · 68 tokens per session scan A 5d62ba187f61
bot_setup is a skill published in the GitHub repository vibeinging/YiYi (51 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 68 tokens to every session and 2,039 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…