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/sfc-gh-dflippo/snowflake-dbt-demoWrote 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/sfc-gh-dflippo/snowflake-dbt-demo/cursor_rules)<a href="https://agentmods.dev/rules/sfc-gh-dflippo/snowflake-dbt-demo/cursor_rules"><img src="https://agentmods.dev/badge/rules/sfc-gh-dflippo/snowflake-dbt-demo/cursor_rules.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.1 | $0.00374 | $0.00374 |
| Opus 5 | $0.00187 | $0.00187 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
cursor_rules 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 7d 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.
This is a copy
100% identical to cursor-rules-meta-guide — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
-
Required Rule Structure:
--- description: Clear, one-line description of what the rule enforces globs: path/to/files/*.ext, other/path/**/* alwaysApply: boolean --- - **Main Points in Bold** - Sub-points with details - Examples and explanations -
File References:
- Use
[filename](mdc:path/to/file)(filename) to reference files - Example: prisma.mdc for rule references
- Example: schema.prisma for code references
- Use
-
Code Examples:
- Use language-specific code blocks
// ✅ DO: Show good examples const goodExample = true; // ❌ DON'T: Show anti-patterns const badExample = false; -
Rule Content Guidelines:
- Start with high-level overview
- Include specific, actionable requirements
- Show examples of correct implementation
- Reference existing code when possible
- Keep rules DRY by referencing other rules
-
Rule Maintenance:
- Update rules when new patterns emerge
- Add examples from actual codebase
- Remove outdated patterns
- Cross-reference related rules
-
Best Practices:
- Use bullet points for clarity
- Keep descriptions concise
- Include both DO and DON'T examples
- Reference actual code over theoretical examples
- Use consistent formatting across rules
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.
- 7d ago First seen · 54 lines · 374 tokens per session scan A 663e52a544e0
cursor_rules is a cursor rule published in the GitHub repository sfc-gh-dflippo/snowflake-dbt-demo (33 stars, last pushed 23d ago), licensed Apache-2.0. It adds 374 tokens to every session, about $0.0019 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cursor-rules-meta-guide, differing in 5 lines, and is treated as a copy.
Other cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.