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/production-mindsetnpx skills add ash1794/vibe-engineering --skill production-mindsetgit 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/production-mindset)<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/production-mindset"><img src="https://agentmods.dev/badge/skills/ash1794/vibe-engineering/production-mindset.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.00037 | $0.00717 |
| Opus 5 | $0.00018 | $0.00358 |
| Sonnet 5 | $0.00007 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
vibe-production-mindset 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- vibe-production-mindset — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibe-production-mindset
The gap between "works on my machine" and "works in production" is where incidents live.
When to Use This Skill
- Starting any implementation that will run in production
- When implementing API endpoints, data processing, or user-facing features
- Before declaring a feature "done"
- When the user cares about production quality
When NOT to Use This Skill
- Prototypes or spikes explicitly marked as throwaway
- Internal scripts that run once
- Test code (different quality criteria)
- When the user says "just get it working"
The Checklist
Imagine this code serves 1 million users. Check:
1. Observability
- Structured logging at key decision points (not just errors)
- Tracing/correlation ID propagated through the request
- Metrics for key operations (latency, success/failure counts)
- Alerts defined for anomalies
2. Error Handling at System Boundaries
- External API calls have timeouts
- External API calls have retries with backoff
- File I/O handles "file not found" and "permission denied"
- Network errors are handled (connection refused, timeout, DNS failure)
- Database errors are handled (connection lost, constraint violation)
3. Input Validation
- All external input validated before processing
- Size limits on string/array inputs
- SQL injection prevention (parameterized queries)
- XSS prevention (output encoding)
- Authentication checked before authorization
4. Graceful Degradation
- Circuit breakers for external dependencies
- Fallback behavior when dependencies are unavailable
- Graceful shutdown (drain connections, finish in-flight)
- Health check endpoint
5. Resource Management
- Connections closed/returned to pool
- Goroutines/threads have lifecycle management
- Memory bounded (no unbounded growth)
- File handles closed
Steps
- Read the implementation
- Run through the checklist — not every item applies to every feature
- Flag gaps — only for items that DO apply
- Recommend fixes — specific, not generic
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 · 87 lines · 37 tokens per session scan A e9ad8ee7bd7f
vibe-production-mindset is a skill published in the GitHub repository ash1794/vibe-engineering (10 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 717 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-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…
cherry-assistant-guide
从当前安装包查询 Cherry Studio 产品信息并排查运行问题。当用户询问功能、路由、快捷键、Provider、语言、Agent、频道、定时任务、Code CLI、当前版本，或报告运行错误、连接失败、配置异常并需要诊断时触发。.
issue-reporter
只在用户明确要求提交 GitHub Issue、GitHub Bug Report 或 GitHub Feature Request 时使用。用户只说“提交问题”“提交反馈”“上报 bug”“这是个 bug”或描述功能建议但未点名 GitHub 时不得触发，必须改用 cherry-studio-feedback 并默认提交飞书。.