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/jhl-labs/vibe-project/generalgit clone --depth 1 https://github.com/jhl-labs/vibe-projectWrote 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/jhl-labs/vibe-project/general)<a href="https://agentmods.dev/rules/jhl-labs/vibe-project/general"><img src="https://agentmods.dev/badge/rules/jhl-labs/vibe-project/general.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 | $0.00295 | $0.00295 |
| Opus 5 | $0.00148 | $0.00148 |
| Sonnet 5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
general 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 3d 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
General Coding Rules
You are an expert developer working on this project.
Project Context
- Project:
- Description:
- Tech Stack: <language, framework, database>
Core Principles
- Follow existing patterns - Match the codebase style
- Keep it simple - Avoid over-engineering
- Write tests - Cover critical paths
- Handle errors - Never swallow exceptions
Code Quality
- Clean, readable, maintainable code
- Small focused functions (max 30 lines)
- Meaningful names for variables and functions
- Proper error handling
Security (CRITICAL)
NEVER:
- Hardcode secrets or credentials
- Use eval() or dynamic code execution
- Trust user input without validation
- Expose sensitive data in logs
ALWAYS:
- Validate and sanitize all inputs
- Use environment variables for config
- Implement proper error handling
- Use parameterized queries
Git Workflow
- Conventional Commits:
type(scope): description - Atomic commits with clear messages
- Reference issues when applicable
Response Format
When generating code:
- Explain approach briefly
- Provide complete implementation
- Include necessary imports
- Add comments for complex logic
- Suggest tests if applicable
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.
- 3d ago First seen · 59 lines · 295 tokens per session scan A 510ba49a3814
general is a cursor rule published in the GitHub repository jhl-labs/vibe-project (2 stars, last pushed 7mo ago), licensed MIT. It adds 295 tokens to every session, about $0.0015 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
architecture-for-apps
ArchiPy clean architecture for apps — layers, import direction, and base types.
config-and-di
ArchiPy BaseConfig, FastAPIConfig/uvicorn, and DI container wiring.
using-archipy-adapters
Using and writing adapters in ArchiPy apps — extras, ports, mocks, boundary errors.
using-archipy-utils
ArchiPy helpers/utils — pure utilities, AppUtils FastAPI/gRPC factories.
testing-bdd-for-apps
BDD testing for ArchiPy apps — Behave, ScenarioContext, testcontainers.
using-archipy-logics
ArchiPy app logics — business rules, unit of work, domain isolation.