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/obviousworks/vibe-coding-ai-rulesWrote 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/obviousworks/vibe-coding-ai-rules/003-workflow)<a href="https://agentmods.dev/rules/obviousworks/vibe-coding-ai-rules/003-workflow"><img src="https://agentmods.dev/badge/rules/obviousworks/vibe-coding-ai-rules/003-workflow/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/obviousworks/vibe-coding-ai-rules/003-workflow"><img src="https://agentmods.dev/badge/rules/obviousworks/vibe-coding-ai-rules/003-workflow.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.00292 | $0.00292 |
| Opus 5.5 | $0.00117 | $0.00117 |
| Sonnet 5.5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
003-workflow 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
Workflow Standards
Atomic Changes (AC)
Make small, self-contained modifications for traceability and rollback.
Commit Discipline (CD)
Use conventional commit format: type(scope): description Types: feat, fix, docs, style, refactor, test, chore
Change Scope Discipline (CSD)
Only modify files directly related to the current task. Never make unrelated "improvements" without explicit permission.
Context Window Management (CWM)
- Be mindful of AI context limitations
- Keep files focused and modular
- Use file-scoped commands for individual changes
- Only run project-wide commands when explicitly requested
Environment Awareness
- Never modify production environment configurations
- Maintain separate configs for DEV, TEST, PROD
- Never hardcode environment-specific values
Transparent Reasoning (TR)
When generating code, explicitly reference which rules influenced decisions.
Dependency Governance
Never add new dependencies without explicit approval or compelling justification.
Token Efficiency
Use file-scoped commands. Reference docs instead of pasting. Optimize context window usage.
Industry Standards
Follow established conventions for the relevant language and tech stack.
Strategic Documentation
Comment only complex logic or critical functions. Avoid documenting the obvious.
Self-Review Before Commit
After generating code, argue against your own solution. Check for redundancy, unnecessary complexity, or simpler alternatives.
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 · 48 lines · 292 tokens per session scan A 225518a97267
003-workflow is a cursor rule published in the GitHub repository obviousworks/vibe-coding-ai-rules (93 stars, last pushed 4mo ago), licensed MIT. It adds 292 tokens to every session, about $0.0012 per session on Opus 5.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.
Other cursor rules, from other repositories
windsurfrules
Pare wraps CLI tools in MCP servers returning structured JSON. Always prefer Pare MCP tools over raw CLI.
workflow
Git branching strategy, commit conventions, and pull request workflow.
save
Lightweight incremental checkpoint for a long autonomous run — refresh the handoff, commit converged work, and push, fired frequently (after each subagent merge, periodically, and when nearing the rate-limit → then schedule a resume past the window reset). Complements /pause (deliberate one-shot handoff) and /resume…
auto-commit
Read this when user asks you to auto commit as you go.
gjalla-attestation
Report system-level changes and rule adherence for a code commit.
conventional-commits
Always use Conventional Commits for git commit messages.