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/ash1794/vibe-engineering/using-vibe-engineeringnpx skills add ash1794/vibe-engineering --skill using-vibe-engineeringgit clone --depth 1 https://github.com/ash1794/vibe-engineeringWrote 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/ash1794/vibe-engineering/using-vibe-engineering)<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/using-vibe-engineering"><img src="https://agentmods.dev/badge/skills/ash1794/vibe-engineering/using-vibe-engineering.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.00034 | $0.00856 |
| Opus 5 | $0.00017 | $0.00428 |
| Sonnet 5 | $0.00007 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
vibe-using-vibe-engineering 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- vibe-using-vibe-engineering — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibe-using-vibe-engineering
You have access to the vibe-engineering skill collection — 34 engineering discipline skills extracted from real-world development.
How This Works
Before taking any action, check if a vibe-engineering skill applies. Skills use the vibe- prefix.
Skill Quick Reference
Before Building
vibe-research-before-design— SOTA research before proposing architecture/featuresvibe-start-informed— Research agents for real projects, papers, and documented failuresvibe-decision-journal— Record architectural decisions for cross-session memoryvibe-production-mindset— Set "1 million users" quality expectations
While Building
vibe-quality-loop— Implement→Review→Test→Fix→Loop until cleanvibe-scope-guard— Detect and redirect scope creepvibe-anti-rationalization-check— Catch shortcut rationalizationvibe-acceptance-gate— Validate against acceptance criteriavibe-coverage-enforcer— Enforce tiered coverage standardsvibe-concurrent-test-safety— Audit for race conditions in testsvibe-adversarial-test-generation— Generate edge case testsvibe-fuzz-parser-inputs— Fuzz test scaffolding for parsersvibe-golden-file-testing— Snapshot tests with temporal normalizationvibe-pattern-library— Record and suggest established patterns
Before Shipping
vibe-devil-advocate-review— 5-dimension adversarial challengevibe-spec-vs-code-audit— Spec compliance checkvibe-doc-quality-gate— 6-point document quality checkvibe-pre-commit-audit— Secrets, debug statements, TODO scanvibe-safe-deploy— Pre-flight checks with rollbackvibe-rollback-plan— Documented rollback runbookvibe-structured-output— Enforced output format
After Building
vibe-reflect-and-compound— Extract learnings from experiencevibe-debugging-journal— Record bug patternsvibe-iteration-review— Quality grading and trendsvibe-handover-doc— Session continuity document
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 · 83 lines · 34 tokens per session scan A e208577dabd3
vibe-using-vibe-engineering is a skill published in the GitHub repository ash1794/vibe-engineering (10 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 856 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
wechat-article-writer
公众号/自媒体全流程。根据用户表述自动匹配：撰写文章、封面图、正文插图、风格提取。支持多种写作风格。当用户提到写公众号、技术博客、公众号封面、正文插图、步骤图、演示图、流程示意、分析写作风格、克隆文风、模仿爆款、提取风格时使用。详见 reference 目录。.
prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
cherry-assistant-guide
从当前安装包查询 Cherry Studio 产品信息并排查运行问题。当用户询问功能、路由、快捷键、Provider、语言、Agent、频道、定时任务、Code CLI、当前版本，或报告运行错误、连接失败、配置异常并需要诊断时触发。.
cherry-electron-dev
Develop, fix, and profile Cherry Studio in a tracked Electron instance. Use for everyday implementation, UI and interaction work, bug fixing, runtime debugging, DevTools inspection, lag or jank investigation, CPU and memory monitoring, leak checks, and startup-performance analysis; reuse a verified workspace instance…
issue-reporter
只在用户明确要求提交 GitHub Issue、GitHub Bug Report 或 GitHub Feature Request 时使用。用户只说“提交问题”“提交反馈”“上报 bug”“这是个 bug”或描述功能建议但未点名 GitHub 时不得触发，必须改用 cherry-studio-feedback 并默认提交飞书。.