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 instructions/l1anch1/vibeposter/claude-mdgit clone --depth 1 https://github.com/l1anch1/VibePosterWrote 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/instructions/l1anch1/vibeposter/claude-md)<a href="https://agentmods.dev/instructions/l1anch1/vibeposter/claude-md"><img src="https://agentmods.dev/badge/instructions/l1anch1/vibeposter/claude-md.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.01900 | $0.01900 |
| Opus 5 | $0.00950 | $0.00950 |
| Sonnet 5 | $0.00380 | $0.00380 |
| Haiku 4.5 | $0.00190 | $0.00190 |
Grade A, and why
VibePoster CLAUDE.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 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.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibePoster
AI-powered poster design system. Multi-agent orchestration + Knowledge Graph (KG) + RAG brand knowledge + image understanding/generation + online editor.
Project Structure
VibePoster/
├── frontend/ # React 19 + TypeScript + Vite 7 + Tailwind CSS 4
├── backend/
│ ├── engine/ # Python FastAPI — AI Agent engine (LangGraph orchestration)
│ └── render/ # Node.js Express — PNG/JPG/PSD export service
└── docs/ # Architecture docs
Quick Start
Docker (recommended)
cp backend/engine/env.template backend/engine/.env
# Edit .env with your API keys
docker-compose up -d --build # production
docker-compose -f docker-compose.yml -f docker-compose.dev.yml up # dev (hot reload)
Local Development (3 terminals)
# Terminal 1: Engine
cd backend/engine && uv sync
uv run uvicorn app.main:app --reload --host 0.0.0.0 --port 8000
# Terminal 2: Render
cd backend/render && npm install && node src/server.js
# Terminal 3: Frontend
cd frontend && npm install && npm run dev
| Service | Dev Port | Prod Port |
|---|---|---|
| Frontend (Vite) | 5173 | 80 (Nginx) |
| Engine (FastAPI) | 8000 | 8000 |
| Render (Express) | 3000 | 3000 |
Environment Variables
Single config file: backend/engine/.env (template: backend/engine/env.template)
Required API keys: PLANNER_API_KEY, VISUAL_API_KEY, LAYOUT_API_KEY, CRITIC_API_KEY, plus at least one of VISUAL_FLUX_API_KEY or VISUAL_PEXELS_API_KEY.
Each agent supports independent config: {AGENT}_PROVIDER, {AGENT}_API_KEY, {AGENT}_BASE_URL, {AGENT}_MODEL, {AGENT}_TEMPERATURE.
Frontend env vars injected via Vite: VITE_API_URL (default http://localhost:8000), VITE_RENDER_URL (default http://localhost:3000).
Agent Architecture
Planner → Visual → Layout → Critic → [retry Layout or END]
- Planner: 4-Skill pipeline (IntentParse → DesignRule/KG → BrandContext/RAG → DesignBrief/LLM)
- Visual: Image understanding + asset search/generation (Pexels/Flux)
- Layout: Semantic DSL generation + OOP layout engine (7 strategies, dynamic coordinate computation)
- Critic: Dual-path review (JSON structure + visual rendering), retries Layout on failure (up to 2x)
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 · 185 lines · 1,900 tokens per session scan A 972ee221bdf2
VibePoster CLAUDE.md is an instructions file published in the GitHub repository l1anch1/VibePoster (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 1,900 tokens to every session, about $0.0095 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-31.
Other instructions, from other repositories
memora CLAUDE.md
Claude Code instructions for agentic-box/memora, covering memora and memory.
robosystems CLAUDE.md
Claude Code instructions for RoboFinSystems/robosystems, covering claude.md - robosystems development guide, critical rules, api endpoints (local testing), health check and extensions operation write (close a period).
council-lab AGENTS.md
AGENTS.md instructions for loveramarois-byte/council-lab, covering council lab engineering rules, high-risk decision support, change discipline, macos desktop delivery and required review focus.
James-RAG-Evol CLAUDE.md
Claude Code instructions for Hashevolution/James-RAG-Evol, covering sekos / james — session briefing for claude code, what james is, where we are right now, critical rules for this session and where to look next.
ai-video-studio AGENTS.md
Instructions for yfge/ai-video-studio, covering agents guidance for ai-video-studio, instruction order, repository mission, agent system of record and working rules.
WorldOfTaxonomy CLAUDE.md
Instructions for colaberry/WorldOfTaxonomy, covering claude.md - worldoftaxonomy, what this project is, architecture, tech stack and how to run.