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/jpke/cursor-vibe-coding-templateWrote 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/jpke/cursor-vibe-coding-template/development)<a href="https://agentmods.dev/rules/jpke/cursor-vibe-coding-template/development"><img src="https://agentmods.dev/badge/rules/jpke/cursor-vibe-coding-template/development/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/rules/jpke/cursor-vibe-coding-template/development"><img src="https://agentmods.dev/badge/rules/jpke/cursor-vibe-coding-template/development.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.00000 | $0.00326 |
| Opus 5.5 | $0.00000 | $0.00130 |
| Sonnet 5.5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
development 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.
What it actually says
Frontend Development
- MVP Development Workflow:
- Start with HTML: Every application MVP, regardless of its final platform (e.g., mobile app), should begin as a basic HTML page. This enables rapid prototyping and iteration.
- Styling Guidelines: If you provide a
design.jsonfile, I will use it as the primary guideline for all styling and visual design choices.
Testing Strategy
- Test-Driven Development: Adopt a TDD approach where possible. At a minimum, ensure that unit tests are created or updated for any new or modified code.
- Test Completion: All tests must be passing before a coding task is considered complete.
- Test Output: All test reports, artifacts, and error logs must be output to a common
tests_output/directory at the project root.
Python Environment Management
- Virtual Environments: Always use a virtual environment (
venv) when running Python scripts. Check for an existingvenvin the current or parent directories before creating a new one. Activate thevenvbefore installing packages or executing scripts.
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 · 19 lines · 0 tokens per session scan A d93928d67868
development is a cursor rule published in the GitHub repository jpke/cursor-vibe-coding-template (16 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 326 tokens. 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.
Other cursor rules, from other repositories
reqforge-core
Forge core development rules — code standards, TDD discipline, verification gates, memory system, and feedback loop. Applies to all code files.
80-testing-quality
Testing and code quality rules.
refactoring
Refactoring: systematic approach, extract/inline, guard clauses, early returns.
incremental-verify
Verify each behavior before building the next. One test, one implementation, one commit. No bulk-writing tests for behavior that does not yet exist.
90-devops-deployment
Docker, CI/CD, AWS, Vercel, and VPS deployment rules.
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.