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 qGolem/orc --skill vibe-codegit clone --depth 1 https://github.com/qGolem/orcWrote 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/qgolem/orc/vibe-code)<a href="https://agentmods.dev/skills/qgolem/orc/vibe-code"><img src="https://agentmods.dev/badge/skills/qgolem/orc/vibe-code/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/qgolem/orc/vibe-code"><img src="https://agentmods.dev/badge/skills/qgolem/orc/vibe-code.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.00015 | $0.01227 |
| Opus 5.5 | $0.00006 | $0.00491 |
| Sonnet 5.5 | $0.00003 | $0.00245 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
vibe-code 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 1mo 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe Code
From loaded spec: Refer to the loaded design system spec for: color palette, typography, border system, layout patterns, component library, CSS setup, shadows, breakpoints. Brand-specific constraints (theme mode, package manager, border values) are defined in the loaded spec.
Brand-specific antipatterns (e.g., wrong color palette, incorrect border widths) are defined in the loaded design system spec under "System-Specific Constraints".
Design Iterator (xN in parallel):
- Ask it to fix one thing at a time from the screenshot analysis
- Takes screenshots
- Analyzes visual gaps systematically
- Implements ONE improvement per iteration
- References loaded design system patterns
- Stops when design is polished
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.
- 1mo ago First seen · 162 lines · 15 tokens per session scan A 6154b00d0910
vibe-code is a skill published in the GitHub repository qGolem/orc (5 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 1,227 once invoked, about $0.0001 per session on Opus 5.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
recipe-front-adjust
Adjust an already-implemented UI in-session with verification against the design source.
recipe-front-design
Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval.
fidelity-gate
Build a UI against a frozen visual reference without drift - an inventory extracted before any code, a relics list, and a gate that MEASURES computed styles on a fixture carrying the reference's own data. Use when a mockup, design spec or screenshot is the contract.
a11y-audit
Dedicated WCAG 2.2 AA/AAA accessibility audit across 10 dimensions (A1-A10) covering semantic HTML, keyboard navigation, ARIA patterns, color contrast, forms, images/media, responsive/zoom, motion/animation, reading/content, and legal compliance. Goes far beyond surface-level design-review checks with deep…
design-review
UI/UX design consistency audit. Code-based DX1-DX20 checklist covering states, consistency, accessibility, responsive behavior, and interaction patterns. Optional visual audit via chrome-devtools screenshots and automated WCAG accessibility via axe-core. DAP1-DAP12 anti-pattern detection. Modes: [path], visual…
design
Intent-first UI design with conscious, traceable design decisions. Persists decisions in .interface-design/ for cross-session consistency. Includes domain exploration, design system generation (system.md + system.json), per-component construction with mandatory checkpoints, and craft validation tests. Modes: init…