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/mracal/vibe-engineering/using-vibe-engineeringnpx skills add mracal/vibe-engineering --skill using-vibe-engineeringgit clone --depth 1 https://github.com/mracal/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/mracal/vibe-engineering/using-vibe-engineering)<a href="https://agentmods.dev/skills/mracal/vibe-engineering/using-vibe-engineering"><img src="https://agentmods.dev/badge/skills/mracal/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.1 | $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 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.
This is a copy
100% identical to vibe-using-vibe-engineering — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 5d ago First seen · 83 lines · 34 tokens per session scan A e208577dabd3
vibe-using-vibe-engineering is a skill published in the GitHub repository mracal/vibe-engineering (3 stars, last pushed 2d 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. It is 100% identical to vibe-using-vibe-engineering, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
codexkit-repository-maintenance
Use when maintaining or improving the GameStudio-CodexKIT source repository, including CI, governance, catalog, generators, adapters, packaging, documentation, versioning, or release readiness.
unity-ui-art-and-motion-production
Use when new or revised Unity UI visuals, icons, panels, 9-slice sprites, component states, HUD or menu layouts, popup motion, screen transitions, or flattened UI screenshot decomposition must be produced through Figma and integrated into uGUI, NGUI, or UI Toolkit; not for UI debugging, localization-only work…
game-screenshot-showcase-and-store-packaging
Use when a Unity team needs approved PlayMode screenshots, immutable capture evidence, reviewed showcase slides, or report-only store screenshot packaging without auto-upload, signing, or submission.
studio-project-scaffold
Use when running gamestudio init, status, or uninit, or bootstrapping a new or adopted game repository with AGENTS.md, HANDOFF.md, .agents/CONTRACT.md, project governance, a subsystem registry, or a per-project adapter report, plan digest, named reviewer, backup root, generated agent overlay, apply, uninstall, and…
using-game-studio-skills
Use when starting any GameStudio-CodexKIT task or when a model runner is unavailable and someone requests a confidence-based PASS.
animation-rigging-import-audit
Use when character animation needs an audit across skeleton, rig, skin weights, avatar, retargeting, clips, events, root motion, compression, import settings, runtime blending, and platform budgets; not for general art preflight.