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 chentao326/vibe-code --skill vibe-recommendgit clone --depth 1 https://github.com/chentao326/vibe-codeWrote 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/chentao326/vibe-code/vibe-recommend)<a href="https://agentmods.dev/skills/chentao326/vibe-code/vibe-recommend"><img src="https://agentmods.dev/badge/skills/chentao326/vibe-code/vibe-recommend.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.00045 | $0.00381 |
| Opus 5 | $0.00023 | $0.00191 |
| Sonnet 5 | $0.00009 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
vibe-recommend 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 6d 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
vibe-recommend — 任务优先级推荐
读 tasks/ 目录 + state + rubric → 推荐任务顺序。
Workflow
Phase 1: 读状态
读 .vibe-state.json → WIP 数量、calibration_samples。
Phase 2: 读候选任务
Glob tasks/*.md，排除已在 WIP 的任务。
Phase 3: 排序推荐
推荐逻辑：
- 排除：已在 WIP 的任务
- 排序：按综合分降序（如有评估数据），否则按文件名
- 分组：
- 第 1 个（稳分）：CS + AQ 高，CX 低（需求清晰 + AI 匹配好 + 改动小 = 快速完成）
- 第 2 个（实验性）：能验证某个待验证假设的任务
Phase 4: 输出
🎯 推荐任务
稳分（建议优先）:
• tasks/fix-typo.md — CS=5, AQ=5, CX=1 → 预计 1-2 轮，5-10min
实验性（验证假设）:
• tasks/refactor-db.md — CX=4, AM=3 → 适合验证"高 CX 任务是否系统性被低估"
⚠️ 提醒：当前 WIP=3（偏高），建议先完成已有任务。
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.
- 6d ago First seen · 46 lines · 45 tokens per session scan A aeee1c12fc30
vibe-recommend is a skill published in the GitHub repository chentao326/vibe-code (2 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 381 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…