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/bernierllc/agents-environment-configWrote 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/bernierllc/agents-environment-config/readme)<a href="https://agentmods.dev/rules/bernierllc/agents-environment-config/readme"><img src="https://agentmods.dev/badge/rules/bernierllc/agents-environment-config/readme/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/bernierllc/agents-environment-config/readme"><img src="https://agentmods.dev/badge/rules/bernierllc/agents-environment-config/readme.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.01150 | $0.01150 |
| Opus 5.5 | $0.00460 | $0.00460 |
| Sonnet 5.5 | $0.00230 | $0.00230 |
| Haiku 4.5 | $0.00115 | $0.00115 |
Grade A, and why
README 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 19d 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Rules Index
Overview
This directory follows a MECE (Mutually Exclusive, Collectively Exhaustive) structure to make rules discoverable and scoped by concern. High-level categories are: general, languages, stacks, frameworks, topics, and packages.
Global vs Project-Specific Rules
This repository contains global rules that apply across all projects. These rules cover:
- General patterns and standards
- Language-specific conventions (TypeScript, Python)
- Framework standards (Next.js, FastAPI, React Native)
- Cross-cutting topics (API design, Git workflow, security, quality)
- Testing and accessibility standards
Project-specific rules should remain in their respective projects (e.g., my-project/.cursor/rules/) and should:
- Reference global rules where applicable
- Focus on project-specific patterns and business logic
- Avoid duplicating global standards
How it works: Cursor IDE automatically discovers rules in parent directories. When this repository is in your workspace path, Cursor will apply these global rules alongside project-specific rules (project rules take precedence for conflicts).
For architecture details, see plans/cursor/architecture.md.
Structure
general/
Always-apply rules that apply universally across all projects:
architecture.mdc- Core architectural principles and design philosophydevelopment-workflow.mdc- Version control, code quality, and development environment standardsdocumentation.mdc- Documentation standards, file organization, and content guidelinessecurity.mdc- Security standards, authentication, authorization, and data protectionport-management.mdc- Centralized port management system to prevent conflictsplans-checklists.mdc- Plans and checklist usage standardsrules-about-rules.mdc- Rules for managing and maintaining cursor rules files
languages/
Language-specific rules (apply when working with these languages):
python/style.mdc- PEP 8, Black formatting, type hints, code organizationtypescript/typing-standards.mdc- TypeScript typing standards, strict mode, no any
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.
- 19d ago Changed · -1 lines · -15 tokens per session e880ee2710eb
- 1mo ago First seen · 102 lines · 1,165 tokens per session scan A 65e3bed50a91
README is a cursor rule published in the GitHub repository bernierllc/agents-environment-config (11 stars, last pushed 10d ago), licensed MIT. It adds 1,150 tokens to every session, about $0.0046 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-31.
Other cursor rules, from other repositories
QUICK_START
Quick-start playbook for rule discovery - first-run steps, task-to-rule shortcuts, and fallback when project context is missing.
ia-navigation-and-structure
Information architecture patterns for navigation, structure, and labeling.
project-structure
Project structure guidelines for Optimizely Configured Commerce development.
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.