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/spec-vs-code-auditnpx skills add ash1794/vibe-engineering --skill spec-vs-code-auditgit 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/spec-vs-code-audit)<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/spec-vs-code-audit"><img src="https://agentmods.dev/badge/skills/ash1794/vibe-engineering/spec-vs-code-audit.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.00485 |
| Opus 5 | $0.00017 | $0.00243 |
| Sonnet 5 | $0.00007 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
vibe-spec-vs-code-audit 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 3d 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-spec-vs-code-audit — 100% identical, 0 lines differ
What it actually says
vibe-spec-vs-code-audit
Specs drift from code. Code drifts from specs. This skill catches the gaps.
When to Use This Skill
- Implementation of a spec/design doc is claimed complete
- After a major refactor that should still conform to a spec
- During periodic compliance checks
- When debugging unexpected behavior (maybe the code doesn't match the spec)
When NOT to Use This Skill
- No spec or design doc exists (nothing to compare against)
- The spec is explicitly marked as aspirational/future
- Code was intentionally diverged with documented reasons
Steps
-
Identify the spec — Find the specification document (design doc, PRD section, API spec, etc.)
-
Identify the implementation — Find the code files that implement this spec
-
Line-by-line comparison — For each requirement/section in the spec:
- Find the corresponding code
- Check: Does the code match the spec exactly?
- If divergent: Record as a GAP
-
Classify each gap:
- ID: GAP-[section]-[number] (e.g., GAP-AUTH-001)
- Type: Missing (spec says X, code has nothing) / Incorrect (spec says X, code does Y) / Extra (code has X, spec doesn't mention it)
- Severity: Critical (breaks core functionality) / High (wrong behavior) / Medium (incomplete) / Low (cosmetic)
-
Report:
Output Format
Spec vs Code Audit
Spec: [document name/path] Implementation: [code path(s)] Gaps Found: X (Y critical, Z high)
| GAP ID | Type | Severity | Spec Says | Code Does |
|---|---|---|---|---|
| GAP-AUTH-001 | Missing | Critical | "Tokens expire after 24h" | No expiration logic found |
Top 3 Risks
- [Most dangerous gap]
Recommended Fix Order
- [Fix critical gaps first]
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.
- 3d ago First seen · 59 lines · 34 tokens per session scan A 6fe659ea613b
vibe-spec-vs-code-audit 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 485 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 并默认提交飞书。.