Borrowing it
Nothing to install: this file belongs to BuaaJoseph/claude-code-best-practice-zh. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/BuaaJoseph/claude-code-best-practice-zh/master/.claude/skills/presentation/vibe-to-agentic-framework/SKILL.mdgit clone --depth 1 https://github.com/BuaaJoseph/claude-code-best-practice-zhWrote 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/buaajoseph/claude-code-best-practice-zh/vibe-to-agentic-framework)<a href="https://agentmods.dev/skills/buaajoseph/claude-code-best-practice-zh/vibe-to-agentic-framework"><img src="https://agentmods.dev/badge/skills/buaajoseph/claude-code-best-practice-zh/vibe-to-agentic-framework/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/buaajoseph/claude-code-best-practice-zh/vibe-to-agentic-framework"><img src="https://agentmods.dev/badge/skills/buaajoseph/claude-code-best-practice-zh/vibe-to-agentic-framework.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.03286 |
| Opus 5.5 | $0.00021 | $0.01314 |
| Sonnet 5.5 | $0.00010 | $0.00657 |
| Haiku 4.5 | $0.00005 | $0.00329 |
Grade A, and why
vibe-to-agentic-framework 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 1mo 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
"从Vibe Coding到代理工程"框架
此技能教授演示文稿背后的概念模型。每张幻灯片和章节都讲述一个故事:开发者如何逐步从无结构的"vibe coding"(低级)迈向高级代理工程(高级)。
核心概念
**Vibe Coding(低级)**是指开发者使用Claude Code但没有任何结构——没有项目上下文、没有约定、没有可复用知识。每个提示都是抛硬币。Claude可能会创建随机端点、忽略现有模式、跳过测试,产生不一致的代码。代码库随着每次交互趋向熵增。
**Agentic Engineering(高级)**是指Claude Code作为完全配置的工程系统运行。它知道项目架构(CLAUDE.md)、遵循作用域约定(Rules)、按需加载领域专业知识(Skills)、委托给专业 worker(Agents)、编排多步骤工作流(Commands)、自动化生命周期事件(Hooks)、连接外部工具(MCP Servers)。每个提示都产生一致、经过测试的生产级代码。
这两个极端之间的旅程是渐进式和累积性的。每个最佳实践都建立在前一个之上,演示文稿按照开发者应该采用的顺序来教授。
4级旅程系统
演示文稿使用4级评分系统而非百分比条:
| 级别 | 顺序 | 颜色 | 旅程条高度 | 描述 |
|---|---|---|---|---|
| Low | 1 | 红色/橙色 (hsl(0, 70%, 45%)) |
25% | Vibe coding领地——无结构 |
| Medium | 2 | 黄色 (hsl(40, 70%, 45%)) |
50% | 结构化工作流,部分自动化 |
| High | 3 | 浅绿色 (hsl(80, 70%, 45%)) |
75% | 领域知识、技能、自定义代理 |
| Pro | 4 | 深绿色 (hsl(120, 70%, 45%)) |
100% | 完整代理工程,多代理团队 |
旅程条在幻灯片1(标题幻灯片)隐藏,从幻灯片2开始显示。级别通过关键过渡幻灯片上的 data-level 属性设置,随后幻灯片继承该级别直到下一个级别变化。当级别变化时,.level-badge 由JS注入到幻灯片的 h1 中(不要在HTML中硬编码这些)。
运行示例:TodoApp Monorepo
每种技术都在一个现实的全栈项目中演示。演示文稿展示了从纯项目(vibe coding)到完整Claude Code配置(代理工程)的转变:
之前(Vibe Coding):
todoapp/
├── backend/ # FastAPI (Python)
│ ├── main.py
│ ├── routes/
│ ├── models/
│ └── tests/
└── frontend/ # Next.js (TypeScript)
├── components/
├── pages/
└── lib/
之后(Agentic Engineering):
todoapp/
├── .claude/ # Claude Code 配置
│ ├── agents/ # 自定义子代理
│ ├── skills/ # 领域知识
│ ├── commands/ # 斜杠命令
│ ├── hooks/ # 生命周期脚本
│ ├── rules/ # 模块化指令
│ ├── settings.json # 团队设置
│ └── settings.local.json # 个人设置
├── backend/
│ └── CLAUDE.md # 后端指令
├── frontend/
│ └── CLAUDE.md # 前端指令
├── .mcp.json # 管理的MCP服务器
└── CLAUDE.md # 项目指令
为什么选TodoApp? 它足够小以适应幻灯片,但足够复杂以展示真实问题:一个后端有路由模式和测试约定,一个前端有组件层次结构和设计代币,以及一个需要跨领域关注点协调(如添加新功能)的monorepo结构。
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.
- 1mo ago First seen · 170 lines · 52 tokens per session scan A 4e107bca1554
vibe-to-agentic-framework is a skill published in the GitHub repository BuaaJoseph/claude-code-best-practice-zh (2 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 3,286 once invoked, about $0.0002 per session on Opus 5.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
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.