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/timurgaleev/vibestackWrote 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/timurgaleev/vibestack/anti-patterns)<a href="https://agentmods.dev/rules/timurgaleev/vibestack/anti-patterns"><img src="https://agentmods.dev/badge/rules/timurgaleev/vibestack/anti-patterns/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/timurgaleev/vibestack/anti-patterns"><img src="https://agentmods.dev/badge/rules/timurgaleev/vibestack/anti-patterns.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.00613 | $0.00613 |
| Opus 5 | $0.00307 | $0.00307 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
anti-patterns 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 yesterday.
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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Anti-Patterns
The single source for traps worth naming. Every item is written as an action — "do not do X", or "do Y instead of X" — so it is checkable against a diff.
Use this as a self-review pass before a commit or PR.
Code Quality
- Editing code without reading the context around it.
- Introducing a new pattern that ignores the project's conventions.
- Adding exception handling instead of finding the root cause.
- Broad
catchblocks that swallow the failure. - Premature optimization or abstraction.
- Mutating an object where a new one would do.
- Ignoring failures, warnings, or edge cases surfaced by the tooling.
Scope
- Adjacent refactors and style changes beyond the request.
- Deleting unrelated dead code instead of mentioning it.
- Slipping in a new abstraction, flag, or configuration option nobody asked for.
- Mixing two purposes into one commit or PR.
- A 200-line diff for a one-line bug fix.
Problem Solving
- Quick fixes applied without understanding the cause.
- Treating symptoms (try/catch everywhere) instead of causes.
- Stopping at the first plausible explanation.
- Starting without an exit condition ("let's try and see").
- Calling work done without verifying it.
Testing
- Replacing every integration test with mocks.
- Tests that share state or depend on execution order.
- Changing the test to match the implementation when the test was right.
Git & Deployment
- Committing or pushing without explicit permission.
- Bypassing hooks or signing (
--no-verify,--no-gpg-sign). - Force-pushing a shared branch.
- Committing secrets, binaries, or generated files.
- Tool-attribution trailers in commits or PR bodies (see
rules/authorship.md).
Tooling
- Running independent tool calls sequentially for no reason.
- Guessing at a skill or agent that does not exist.
- Large refactors in the last stretch of the context window.
Documentation
- Accumulating past state, change history, and dead ends in docs and comments. Record only the current state — git and PRs are the history.
- Leaving a comment that no longer matches the code. Delete it rather than let it mislead.
- Comments that restate the code instead of explaining why.
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.
- yesterday First seen · 79 lines · 613 tokens per session scan A 917a3f699313
anti-patterns is a cursor rule published in the GitHub repository timurgaleev/vibestack (6 stars, last pushed yesterday), licensed MIT. It adds 613 tokens to every session, about $0.0031 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-09-19.
Other cursor rules, from other repositories
pr-code-review
Code review rule for PR analysis. Challenges architectural decisions, examines the diff with the default branch, and provides comprehensive feedback on code quality, security, performance, and maintainability before publishing.
MANDATORY_BEHAVIORAL_FIREWALL
🛡️ AI Code Quality Control System for Cursor IDE - Prevents low-quality code by enforcing mandatory research protocols before modifications. Optimized for Rust/Bevy stack with universal support via Context7 & web search.
refactorer
Refactorer agent.
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.