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 matteotitta/genesys-skills --skill vibe-codinggit clone --depth 1 https://github.com/matteotitta/genesys-skillsWrote 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/matteotitta/genesys-skills/vibe-coding)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/vibe-coding"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/vibe-coding/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/matteotitta/genesys-skills/vibe-coding"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/vibe-coding.svg" alt="Reviewed on agentmods" width="80" 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.00111 | $0.03256 |
| Opus 5 | $0.00056 | $0.01628 |
| Sonnet 5 | $0.00022 | $0.00651 |
| Haiku 4.5 | $0.00011 | $0.00326 |
Grade A, and why
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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe coding
Plan an app, lead magnet, or interactive tool build using Lovable or Claude Code. Produce a project spec, tech-stack recommendation, seed prompt, iteration plan, and deployment path. Knowledge type: landing-page-copy (per .claude/rules/ontology.md); maturity: emergent → validated after first deployment.
Doctrine inherited (Step 7 — 0626 rollout, locked 2026-06-04)
Output complies with output-tenets.md, output-simplicity.md, design-production.md. Step 6 calibration: see [[feedback_execution_doctrine_refinements_step6]].
Refinements applied: R1 (project spec is client-team review surface — cites in appendix; rendered app is end-customer-facing — no source frames), R3 (app copy capability-led across hero + body), R6 (app close → sign-up primary for lead magnets, product-action for interactive tools), R9 (verb-led spec section names).
When to run
Invoke when the user says: "vibe code [something]", "build an app for [purpose]", "create a tool that [does X]", "make a website for [purpose]", "deploy to Vercel", "Claude Code project", "Lovable project", "build a quiz / calculator / lead magnet", "I have an idea but don't know where to start". Do NOT invoke for: landing-page copy only (use /landing-page-copy), design guidelines (use /brand-kit), debugging existing code (handle directly), or in-tool prompt creation (use /workflow-prompt-design).
This skill is guided planning + iterative prompting, not direct code writing. The user (or another agent) executes the build inside Lovable or Claude Code; this skill produces the brief, the seed prompt, and the iteration coaching.
The Iron Law: one variable per iteration. Multi-variable edits degrade quality. If circling, re-anchor with stronger references — don't keep iterating against weak anchors.
Inputs
Required:
project idea— what the user wants to build (e.g., "GTM readiness quiz", "ROI calculator").tool preference— Lovable or Claude Code (or "help me choose").
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.
- 10d ago First seen · 174 lines · 111 tokens per session scan A 7dc5469bf600
vibe-coding is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 111 tokens to every session and 3,256 once invoked, about $0.0006 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-30.
Other skills, from other repositories
gingiris-b2b-growth
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns.…
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
gr-b2b-growth
A guide to growing a business-to-business software product from early user research to large-scale sales. B2B software is sold to companies rather than individual consumers.
gingiris-go-global
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles.…
gr-competitor-research
Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI…
ai-launch-playbook
Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.