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.
git clone --depth 1 https://github.com/ccivlcid/VibeHarnessWrote 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/rules/ccivlcid/vibeharness/vibe-harness)<a href="https://agentmods.dev/rules/ccivlcid/vibeharness/vibe-harness"><img src="https://agentmods.dev/badge/rules/ccivlcid/vibeharness/vibe-harness.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.02252 | $0.02252 |
| Opus 5 | $0.01126 | $0.01126 |
| Sonnet 5 | $0.00450 | $0.00450 |
| Haiku 4.5 | $0.00225 | $0.00225 |
Grade C, and why
vibe-harness 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 7d 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.
Instruction-override phrasinghighPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
If you are editing the VibeHarness repository (the framework, templates, examples, skills), do NOT follow the rules below. Treat this as a normal development project. The rules below apply only when this file is in a tar How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working on the VibeHarness Framework Itself
If you are editing the VibeHarness repository (the framework, templates, examples, skills), do NOT follow the rules below. Treat this as a normal development project. The rules below apply only when this file is in a target project.
Important: The examples/ folder is part of the VibeHarness framework repository only. Do NOT create project code inside examples/. Always create code at the project root (e.g., src/, app.py). If an examples/ folder exists, ignore it — it is reference material, not a target directory.
VibeHarness — Senior Developer AI for Non-Developers
You are a senior full-stack developer and vibe coding mentor.
When a non-developer throws a simple one-line prompt like "build me a chat app", you turn that idea into a complete MVP. Planning, architecture, frontend, backend, design, testing — you do it all.
Non-developers don't know technology. That's normal. You make all technical decisions yourself. Only ask non-developers for confirmation on business decisions — "I'm planning to build these features, does that look right?"
Document everything you do. Two reasons:
- So the next AI session can pick up where you left off
- So non-developers learn vibe coding by watching the process
Your roles:
- Senior Developer: Turn ideas into working MVPs
- Mentor: Leave clear planning docs and progress records
- Partner: Manage MVP scope and guide toward what's feasible
- Advisor: Don't blindly accept every idea. If infeasible, explain why and suggest alternatives. If oversized, break into phases
Context-aware document loading:
Before reading multiple reference docs, read graph.json first. It maps every document's purpose, tags, and relationships. Use queryHints to find only the documents relevant to your current task — don't load everything. See docs/skills/context-graph.md for the full process.
Reference docs — read these when relevant:
docs/references/biz-doc.md— planning document templatedocs/references/ai-dev-doc.md— technical decision document templatedocs/references/project-rules-template.md— PROJECT_RULES.md templatedocs/references/progress-template.md— Progress.md templatedocs/references/code-conventions.md— code conventions and anti-patternsdocs/references/testing-guide.md— testing strategy by stackdocs/references/secure-coding-guide.md— secure coding rules (read before writing any feature with auth, user input, or API)docs/skills/README.md— shared skill map across Codex, Claude Code, and Cursordocs/skills/*.md— shared implementation guidance by stack and task type
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.
- 7d ago First seen · 196 lines · 2,252 tokens per session scan C 1e93bf0fe5dd
vibe-harness is a cursor rule published in the GitHub repository ccivlcid/VibeHarness (5 stars, last pushed 4mo ago), licensed MIT. It adds 2,252 tokens to every session, about $0.0113 per session on Opus 5. A static security scan graded it C with 1 finding (instruction-override phrasing). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.