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 skills add roedyrustam/vibes-plug --skill production-ready-hardenergit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/production-ready-hardener)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/production-ready-hardener"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/production-ready-hardener/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/roedyrustam/vibes-plug/production-ready-hardener"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/production-ready-hardener.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 242 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- high Agent Snooping · line 426 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- high Agent Snooping · line 460 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- high Agent Snooping · line 461 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- high Agent Snooping · line 462 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
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.00077 | $0.07835 |
| Opus 5 | $0.00039 | $0.03918 |
| Sonnet 5 | $0.00015 | $0.01567 |
| Haiku 4.5 | $0.00008 | $0.00783 |
Grade A, and why
production-ready-hardener scanned grade A with 1 finding 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 7d 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
An automated Python scanner script is included at [production_readiness_scanner.py](file:///c:/Users/roedy/.gemini/config/plugins/vibes-plug/skills/production-ready-hardener/scripts/production_readiness_scanner.py) to pe Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production-Ready Hardener
English
Orchestration & Integration
Connects and orchestrates with relevant domain skills like brainstorming, zero-to-prod-orchestrator, and project-context-mapper to ensure cohesive execution.
Description
The Production-Ready Hardener is a master orchestrator skill that combines and delegates to all relevant vibes-plug skills to ensure your application is rock-solid, secure, performant, and production-grade before deployment. It acts as a comprehensive pre-production checklist that leaves no stone unturned — from frontend polish to backend resilience, from data security to observability.
This skill does NOT replace individual skills — it coordinates them into a structured, phased audit-and-hardening workflow.
Orchestrated Skills Map
┌──────────────────────────────────────────────────────────────────┐
│ PRODUCTION-READY HARDENER │
│ (Master Orchestrator — 7 Phases) │
├──────────────────────────────────────────────────────────────────┤
│ │
│ ┌─── PHASE 1: Architecture & Code Quality ───────────────────┐ │
│ │ • scalability-clean-code (SOLID, DRY, Clean Architecture) │ │
│ │ • fullstack-expert / senior-fullstack (Design & patterns) │ │
│ │ • app-analyzer-optimizer (Deep codebase & bottleneck audit)│ │
│ │ • monorepo-architect (Turborepo & pnpm workspace structure)│ │
│ │ • dependency-upgrade-migrator (Codemod & package audits) │ │
│ │ • vibe-code-gardener (Purge AI slop & context drift) │ │
│ │ • typescript-expert (Strict mode & type-safe patterns) │ │
│ └────────────────────────────────────────────────────────────┘ │
│ │
│ ┌─── PHASE 2: Frontend Hardening ────────────────────────────┐ │
│ │ • senior-frontend (React 19, Next.js 15 App Router) │ │
│ │ • design-system-architect (Tokens, Radix, CVA, WCAG 2.2) │ │
│ │ • tailwind-expert (CSS-first config, OKLCH, responsive) │ │
│ │ • form-validation-expert (React Hook Form, Zod validation)│ │
│ │ • state-management-expert (Zustand, Jotai, TanStack Store)│ │
│ │ • ui-components-expert (Input, nav, container primitives) │ │
│ │ • ui-ux-pro-max / hig (HIG principles & design system) │ │
│ │ • global-a11y-i18n-expert (Web accessibility & i18n) │ │
│ │ • mobile-expo-expert / tauri-expert (Mobile & Desktop) │ │
│ └────────────────────────────────────────────────────────────┘ │
│ │
│ ┌─── PHASE 3: Backend & AI Services ─────────────────────────┐ │
│ │ • js-backend-expert (Node 24, Bun 1.2, Fastify, Hono) │ │
│ │ • go-programming-expert (Go 1.24+, microservices, gRPC) │ │
│ │ • python-programming-expert (Python 3.13+, FastAPI, uv) │ │
│ │ • rust-programming-expert (Rust 2024, Axum, async) │ │
│ │ • database-orm-expert (Prisma 6, Drizzle, migrations) │ │
│ │ • edge-serverless-db-expert (Neon, Cloudflare D1, Turso) │ │
│ │ • cron-scheduler-expert / async-queue-temporal-expert │ │
│ │ • email-notification-expert (Transactional emails) │ │
│ │ • file-upload-media-expert (S3, Presigned URLs, CDN) │ │
│ │ • mcp-server-architect (MCP Server Tools & Zod schemas) │ │
│ │ • multi-agent-orchestration / ai-llm-integration-expert │ │
│ │ • ai-cost-token-optimizer (Prompt caching & token budget) │ │
│ └────────────────────────────────────────────────────────────┘ │
│ │
│ ┌─── PHASE 4: Security Hardening ────────────────────────────┐ │
│ │ • supabase-security-expert (RLS policies, Supabase Linter)│ │
│ │ • firebase-security-expert (Rules, App Check, data leak) │ │
│ │ • authentication-identity-expert (OAuth2, RBAC/ABAC) │ │
│ │ • zero-trust-secret-vault (Vault, Infisical, key rotation)│ │
│ │ • rate-limit-abuse-prevention (Rate limit & bot protection)│ │
│ │ • secure-fuzz-testing (Coverage-guided fuzzing) │ │
│ │ • fullstack-expert (OWASP Top 10 & defense-in-depth) │ │
│ └────────────────────────────────────────────────────────────┘ │
│ │
│ ┌─── PHASE 5: Testing & Quality Assurance ───────────────────┐ │
│ │ • e2e-testing-expert (Playwright E2E & Vitest integration)│ │
│ │ • browser-automation-expert (Visual regression testing) │ │
│ │ • secure-fuzz-testing (Security fuzz testing) │ │
│ │ • error-resilience-expert (Retry logic & circuit breakers)│ │
│ │ • logging-error-tracking-expert (Pino, Sentry correlation)│ │
│ │ • coderabbit (AI code review & PR summarization) │ │
│ └────────────────────────────────────────────────────────────┘ │
│ │
│ ┌─── PHASE 6: Performance & GEO/SEO ─────────────────────────┐ │
│ │ • seo (Technical SEO, Schema, Sitemap, E-E-A-T audit) │ │
│ │ • seo-geo (Generative Engine Optimization & llms.txt) │ │
│ │ • seo-aeo-landing-page-writer (AEO conversion landing) │ │
│ │ • performance-web-vitals (CWV: LCP, INP, CLS optimization)│ │
│ │ • app-analyzer-optimizer (Bundle analysis & dynamic loading)│
│ └────────────────────────────────────────────────────────────┘ │
│ │
│ ┌─── PHASE 7: DevOps & Deployment ───────────────────────────┐ │
│ │ • ci-cd-devops-architect (GitHub Actions, Docker, IaC) │ │
│ │ • cloud-hosting-expert (Vercel, Cloudflare Workers, AWS) │ │
│ │ • data-telemetry-expert (OpenTelemetry, PostHog metrics) │ │
│ │ • session-handoff-resume (Save state checkpoint) │ │
│ │ • auto-doc-updater (CHANGELOG & BLUEPRINT automation) │ │
│ └────────────────────────────────────────────────────────────┘ │
│ │
└──────────────────────────────────────────────────────────────────┘
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 463 lines · 77 tokens per session scan A f4fa3ab44079
production-ready-hardener is a skill published in the GitHub repository roedyrustam/vibes-plug (50 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 7,835 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…
update-dependencies
Upgrade project dependencies with breaking change research for major version updates. Use when the user asks to "update dependencies", "upgrade packages", "upgrade dependencies", "update deps", "upgrade deps", "update npm deps", "update Swift packages", "cargo update", "go get updates", "bundle update", or "pip…
review-plan
Review a plan by running internal reviews and a peer review in parallel and returning combined findings. Use when the user asks to "review my plan", "check my plan", "critique my plan", or wants feedback on a plan.
finalize
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
create-changelog
Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".
ai-cold-outreach
When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,'…