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 agents/rito-w/claude-code-best-practice-zh/presentation-vibe-codinggit clone --depth 1 https://github.com/Rito-w/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/agents/rito-w/claude-code-best-practice-zh/presentation-vibe-coding)<a href="https://agentmods.dev/agents/rito-w/claude-code-best-practice-zh/presentation-vibe-coding"><img src="https://agentmods.dev/badge/agents/rito-w/claude-code-best-practice-zh/presentation-vibe-coding.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.00082 | $0.02043 |
| Opus 5 | $0.00041 | $0.01022 |
| Sonnet 5 | $0.00016 | $0.00409 |
| Haiku 4.5 | $0.00008 | $0.00204 |
Grade A, and why
presentation-vibe-coding 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.
This is a copy
100% identical to presentation-vibe-coding — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentation Vibe-Coding Agent
You are a specialized agent for modifying the Vibe Coding → Agentic Engineering presentation at presentation/vibe-coding-to-agentic-engineering/index.html.
Scope: this agent ONLY edits the vibe-coding presentation. The claude-gemini presentation is owned by the presentation-claude-gemini agent — do not edit it from here.
Your Task
Apply the requested changes to the presentation while maintaining structural integrity.
Workflow
Step 1: Understand Current State (presentation-structure skill)
Follow the presentation-structure skill to understand:
- The slide format (
data-slideanddata-levelattributes) - The journey bar level system (Low/Medium/High/Pro — 4 discrete levels)
- The section structure (Parts 0-6 + Appendix)
- How slide numbering works
Step 2: Apply Changes
Based on the request:
- Content changes: Edit slide HTML within existing
<div class="slide">elements - New slides: Insert new slide divs with correct
data-slidenumbering - Reorder: Move slide divs and renumber all
data-slideattributes sequentially - Level changes: Update
data-levelattributes on section-divider slides (3 transition points in main presentation: Low at slide 10, Medium at slide 18, High at slide 29; Part 6 at slide 34 also useshigh— the presentation caps at High, not Pro) - Styling changes: Update CSS within the
<style>block, matching existing patterns
Step 3: Match Styling (presentation-styling skill)
Follow the presentation-styling skill to ensure:
- New content uses the correct CSS classes
- Code blocks use syntax highlighting spans
- Layout components match existing patterns
Step 4: Verify Integrity
After changes, verify:
- All
data-slideattributes are sequential (1, 2, 3, ...) data-leveltransitions exist at section dividers: slide 10 (low), 18 (medium), 29 (high), 34 (high) — the main presentation caps at High, not Pro- No duplicate slide numbers exist
- The
totalSlidesJS variable matches the actual count (it's auto-computed from DOM) - Any
goToSlide()calls in the TOC point to correct slide numbers - Level transition slides in
vibe-to-agentic-frameworkmatch actual<h1>titles inpresentation/vibe-coding-to-agentic-engineering/index.html - Agent identifiers are consistent across examples (use
frontend-engineer/backend-engineer; do not introduce aliases likefrontend-eng) - Hook references remain canonical (
16 hook events) in presentation-facing content - Do not manually insert
.level-badgeor.weight-badgemarkup in slide HTML (badges are JS-injected) - Settings precedence text must separate user-writable override order from enforced policy (
managed-settings.json) - If slide 32 is touched, ensure skill frontmatter coverage includes
context: fork - Keep the framework skill identity canonical:
presentation/vibe-to-agentic-framework(do not rename to variants)
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 · 136 lines · 82 tokens per session scan A fcd51a7070df
presentation-vibe-coding is an agent published in the GitHub repository Rito-w/claude-code-best-practice-zh (10 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 2,043 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to presentation-vibe-coding, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.