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/chentao326/vibe-code/vibe-seednpx skills add chentao326/vibe-code --skill vibe-seedgit 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-seed)<a href="https://agentmods.dev/skills/chentao326/vibe-code/vibe-seed"><img src="https://agentmods.dev/badge/skills/chentao326/vibe-code/vibe-seed.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.00070 | $0.00564 |
| Opus 5 | $0.00035 | $0.00282 |
| Sonnet 5 | $0.00014 | $0.00113 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
vibe-seed 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 5d 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-seed — 找选题
从代码本身提取候选任务。不依赖已有 tasks/ 目录。
Workflow
Phase 1: 多源并行扫描
源1: TODO/FIXME/HACK
grep -rn "TODO\|FIXME\|HACK\|XXX\|WORKAROUND" --include="*.ts" --include="*.js" --include="*.py" --include="*.go" . | head -30
源2: 高频 churn 文件
git log --format=format: --name-only | sort | uniq -c | sort -rn | head -15
源3: 测试覆盖缺口
find . -name "*.ts" -not -name "*.test.ts" -not -name "*.spec.ts" -not -path "*/node_modules/*" | head -50 | while read f; do
test="${f%.ts}.test.ts"; [ ! -f "$test" ] && echo "UNTESTED: $f"
done | head -20
源4: 过期依赖
npx npm-check-updates 2>/dev/null | head -20 || pip list --outdated 2>/dev/null | head -20
源5: 大文件
find . -name "*.ts" -not -path "*/node_modules/*" -exec wc -l {} + | sort -rn | head -10
Phase 2: 分类输出
🌱 选题建议
🔧 技术债（N个）— TODO/FIXME
📦 依赖更新（N个）— 过期/不安全
🧪 测试补全（N个）— 无测试覆盖
♻️ 重构候选（N个）— 高churn/大文件
💡 选感兴趣的，说 "展开 tasks/seed_xxx" 帮你写成正式任务。
Phase 3: 展开
用户选候选 → 写成正式 task 文件到 tasks/<date>_<hash>_<short>.md。
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.
- 5d ago First seen · 57 lines · 70 tokens per session scan A 86aae8c39169
vibe-seed is a skill published in the GitHub repository chentao326/vibe-code (2 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 564 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-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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…