VibeCAD AGENTS.md

VibeCAD AGENTS.md is an instructions file for Codex, OpenCode from rawwerks/VibeCAD. It costs 1,101 tokens per session, scanned A, original, MIT.

A set of project instructions for developers working on the rawwerks/VibeCAD codebase. It explains how to use `bd`, a command-line issue tracker, for planning, dependencies, completion, and syncing work.

In plain words
What is it for?
Setting up work, creating and updating issues, linking dependent tasks, running checks, syncing issue data, and pushing completed changes to the remote repository.
Why use it?
It provides a shared process for turning plans into tracked work and for finishing sessions consistently. It also makes unfinished work and task dependencies visible to the team.

Instructions file for CodexOpenCode

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

Install

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.

agentmods
npx agentmods add instructions/rawwerks/vibecad/agents-md
Clone the repo
git clone --depth 1 https://github.com/rawwerks/VibeCAD

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 VibeCAD AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/rawwerks/vibecad/agents-md.svg)](https://agentmods.dev/instructions/rawwerks/vibecad/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/rawwerks/vibecad/agents-md"><img src="https://agentmods.dev/badge/instructions/rawwerks/vibecad/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,101 This file is loaded in full into every session.
When invoked 1,101 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.01101 $0.01101
Opus 5 $0.00550 $0.00550
Sonnet 5 $0.00220 $0.00220
Haiku 4.5 $0.00110 $0.00110

Measured 6d ago against content hash c1542d0004e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

VibeCAD AGENTS.md 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 6d 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.

AGENTS.md · 134 lines

How it starts

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

Agent Instructions

This project uses bd (beads) for issue tracking. Run bd onboard to get started.

Quick Reference

bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --status in_progress  # Claim work
bd close <id>         # Complete work
bd sync               # Sync with git

Planning

Convert all plans to bd epics/issues with full notes and dependency graphs. When you create a plan file, translate it into:

  • An epic for the overall effort
  • Individual issues for each task
  • Dependencies between issues (bd dep add)
  • Full context in issue bodies

Landing the Plane (Session Completion)

When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.

MANDATORY WORKFLOW:

  1. File issues for remaining work - Create issues for anything that needs follow-up
  2. Run quality gates (if code changed) - Tests, linters, builds
  3. Update issue status - Close finished work, update in-progress items
  4. PUSH TO REMOTE - This is MANDATORY:
    git pull --rebase
    bd sync
    git push
    git status  # MUST show "up to date with origin"
    
  5. Clean up - Clear stashes, prune remote branches
  6. Verify - All changes committed AND pushed
  7. Hand off - Provide context for next session

CRITICAL RULES:

  • Work is NOT complete until git push succeeds
  • NEVER stop before pushing - that leaves work stranded locally
  • NEVER say "ready to push when you are" - YOU must push
  • If push fails, resolve and retry until it succeeds

Adding Skills to VibeCAD

Skill Structure

plugins/<plugin-name>/skills/<skill-name>/
├── SKILL.md              # Required: frontmatter + instructions
└── references/           # Optional: detailed docs, examples
    ├── <reference>.md    # Detailed documentation
    └── examples/         # Runnable example scripts

Progressive Disclosure (Critical)

Skills use a three-level loading system:

  1. Metadata (name + description in frontmatter) - Always in context
  2. SKILL.md body - Loaded when skill triggers
  3. references/ - Loaded as needed by Claude

Read the full file on GitHub · 134 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. 6d ago First seen · 134 lines · 1,101 tokens per session scan A c1542d0004e6

Subscribe to this mod's changes

VibeCAD AGENTS.md is an instructions file published in the GitHub repository rawwerks/VibeCAD (117 stars, last pushed 8mo ago), licensed MIT. It adds 1,101 tokens to every session, about $0.0055 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens