vibe-to-ui: Instructions file for Codex

AGENTS.md

vibe-to-ui AGENTS.md is an instructions file for Codex, OpenCode from MonkeyUI-dev/vibe-to-ui. It costs 2,738 tokens per session, scanned C, original, MIT.

A set of instructions for the Vibe-to-UI repository, an agent skill package with a small command-line tool for managing design context. Design context means saved product and visual guidance that agents use when creating interfaces.

In plain words
What is it for?
Use it when changing the skill package, managing design-context profiles, running its Node.js command-line tool, or validating changes in this repository.
Why use it?
It keeps user profiles and inspiration files separate from the package and prevents installation or updates from overwriting them.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is MonkeyUI-dev/vibe-to-ui's own configuration. It tells Codex and OpenCode how to work on vibe-to-ui itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vibe-to-ui configures →

Reuse

Borrowing it

Nothing to install: this file belongs to MonkeyUI-dev/vibe-to-ui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/MonkeyUI-dev/vibe-to-ui/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/MonkeyUI-dev/vibe-to-ui

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for vibe-to-ui AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/monkeyui-dev/vibe-to-ui/agents-md/github.svg)](https://agentmods.dev/instructions/monkeyui-dev/vibe-to-ui/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/monkeyui-dev/vibe-to-ui/agents-md"><img src="https://agentmods.dev/badge/instructions/monkeyui-dev/vibe-to-ui/agents-md/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.

agentmods 80×15 button for vibe-to-ui AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/monkeyui-dev/vibe-to-ui/agents-md"><img src="https://agentmods.dev/badge/instructions/monkeyui-dev/vibe-to-ui/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,738 This file is loaded in full into every session.
When invoked 2,738 The same file — it is already loaded in full.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02738 $0.02738
Opus 5.5 $0.01095 $0.01095
Sonnet 5.5 $0.00548 $0.00548
Haiku 4.5 $0.00274 $0.00274

Measured 1mo ago against content hash 037c4230f3e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

vibe-to-ui AGENTS.md scanned grade C 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 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf "$HOME"
AGENTS.md · 206 lines

How it starts

The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Cursor Cloud specific instructions

This repository (vibe-to-ui) is primarily an Agent Skill package (Markdown instructions + seed templates), plus a small Node.js zero-dependency CLI for Design Context lifecycle (bin/vibe-to-ui.js, package.json bin). There is still no application server, no build step, no automated test suite, and no linter. Dependencies are not required to use the skill instructions; Node ≥18 is required only when running the vibe-to-ui context CLI. The startup update script is intentionally a no-op.

User Design Context vs skill package

Live Design Context profiles belong under the user home path ~/.vibe-to-ui/profiles/<profile>/, not in this repository. The Inspiration Library belongs under ~/.vibe-to-ui/inspirations/<product>/pages/<page>/ (also user home — not the skill package). Templates under assets/design-context/ are seeds only. Skill install, update, or reinstall must never overwrite, delete, or reset ~/.vibe-to-ui/. There is no env override for the root path.

SKILL.md description (progressive disclosure — do not inflate)

name + description are the only fields loaded at agent startup for every installed skill (Agent Skills progressive disclosure). They must stay small, stable, and optimized for routing (when to activate), not for teaching the full product.

Follow the Agent Skills spec and these repo rules when editing frontmatter:

Rule Requirement
Hard limit description ≤ 1024 characters (spec max). Non-empty.
Soft target Prefer ≈ 400–700 characters (~100–175 tokens). Do not drift toward the hard ceiling.
Job of the field What the skill does + when to use it, with concrete trigger keywords
Not the job Workflow steps, CLI flags, path layouts, open-ended target examples, intake playbooks, long capability catalogs
Activation Include keywords agents match on user intent (e.g. design system, tokens, motion, mood board, spatial layout, visual assets, Design Context, ~/.vibe-to-ui, screenshot, URL, inspiration)
Stability Do not casually rewrite or expand description while implementing features — put detail in the Markdown body or references/

Read the full file on GitHub · 206 lines

Changes

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.

  1. 1mo ago First seen · 206 lines · 2,738 tokens per session scan C 037c4230f3e7

Subscribe to this mod's changes

vibe-to-ui AGENTS.md is an instructions file published in the GitHub repository MonkeyUI-dev/vibe-to-ui (39 stars, last pushed 2mo ago), licensed MIT. It adds 2,738 tokens to every session, about $0.0110 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories