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 rules/sarutobisasuke8/agentops-template/vibe-coding-coregit clone --depth 1 https://github.com/SarutobiSasuke8/agentops-templateWhat 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 | $0.00280 | $0.00280 |
| Opus 5 | $0.00140 | $0.00140 |
| Sonnet 5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
vibe-coding-core 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 2d 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
Vibe Coding Core Rule
Canonical source: AGENTS.md
Follow AGENTS.md. This rule holds Cursor-specific guidance only; the canonical principles live in AGENTS.md.
Alignment Markers
- Think Before Coding — inspect context, surface assumptions, ask when ambiguity changes implementation.
- Simplicity First — prefer the smallest verifiable solution; avoid speculative abstractions and dependencies.
- Surgical Changes — keep edits scoped, preserve existing style, avoid drive-by refactors.
- Goal-Driven Execution — define success criteria and verify changed behavior.
- Vibe Coding Quality Bar — protect the product feeling, responsive UI, core workflows, and polish.
Cursor Behavior
- Inline edits should stay small (target under ~50 lines per accepted edit) unless the user asked for a larger rewrite.
- Ground edits in the current file and nearby project conventions.
- Preserve user-authored comments and docs.
- For UI changes, account for loading, empty, error, hover/focus, and responsive states where relevant.
- Mention unrelated issues separately instead of silently editing them.
- For multi-file, architecture, debugging, or handoff-heavy work, append a session log in
Session Logs/usingTemplates/SESSION_LOG_TEMPLATE.md.
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.
- 2d ago First seen · 28 lines · 280 tokens per session scan A 0c18a1efdab5
vibe-coding-core is a cursor rule published in the GitHub repository SarutobiSasuke8/agentops-template (9 stars, last pushed 13d ago), licensed MIT. It adds 280 tokens to every session, about $0.0014 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 cursor rules, from other repositories
meta-choice-surface
MetaKim choice-surface fallback — stable Cursor trigger for blocking user decisions.
app_rules
This document outlines the essential rules and guidelines for developing with the MobileLauncher LT boilerplate. Follow these rules to maintain consistency, scalability, and code quality across the project.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
database-design
Database design guidelines — relational normalisation, indexing, constraints, NoSQL patterns, query optimisation, migrations, security, and backup strategies. Applied when working with database schemas and queries.
execution
Repository execution and verification commands.
cursorrules
Cursor rule "cursorrules" from evolution-foundation/evo-ai, covering evo ai - project rules and structure, main technologies, project structure, code standards and language requirements.