SnowGram: Command for Claude Code

.cursor/commands/generate-rules.md

generate-rules is a command for Claude Code, Cursor from sfc-gh-abannerjee/SnowGram. It costs 0 tokens per session (364 once invoked), scanned A, original, MIT.

A command for creating or editing Cursor rules, which are Markdown files that tell the Cursor coding assistant how to understand and work with a project.

In plain words
What is it for?
It helps document project structure, define instructions that always apply, and attach rules to selected file patterns or descriptions.
Why use it?
It helps keep project-specific guidance in the expected folder and format so the assistant can apply the right instructions to relevant files or requests.

Command for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code command (commands/*.md). Also seen: mentions Cursor.

This is sfc-gh-abannerjee/SnowGram's own configuration. It tells Claude Code and Cursor how to work on SnowGram itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything SnowGram configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sfc-gh-abannerjee/SnowGram. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sfc-gh-abannerjee/SnowGram/main/.cursor/commands/generate-rules.md
Clone the repo
git clone --depth 1 https://github.com/sfc-gh-abannerjee/SnowGram

Made for: Claude Code, Cursor.

Wrote 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.

agentmods badge for generate-rules

README.md
[![agentmods](https://agentmods.dev/badge/commands/sfc-gh-abannerjee/snowgram/generate-rules/github.svg)](https://agentmods.dev/commands/sfc-gh-abannerjee/snowgram/generate-rules)
Your own site
<a href="https://agentmods.dev/commands/sfc-gh-abannerjee/snowgram/generate-rules"><img src="https://agentmods.dev/badge/commands/sfc-gh-abannerjee/snowgram/generate-rules/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.

agentmods 80×15 button for generate-rules

Your own site · 80×15
<a href="https://agentmods.dev/commands/sfc-gh-abannerjee/snowgram/generate-rules"><img src="https://agentmods.dev/badge/commands/sfc-gh-abannerjee/snowgram/generate-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 364 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00364
Opus 5.5 $0.00000 $0.00146
Sonnet 5.5 $0.00000 $0.00073
Haiku 4.5 $0.00000 $0.00036

Measured 2mo ago against content hash 1ab5afb8abe0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

generate-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 2mo 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.

.cursor/commands/generate-rules.md · 44 lines

What it actually says

Cursor Rules Instructions

To create or edit a rule:

  1. Rules should be stored in the .cursor/rules directory
  2. Rule files must have a .mdc extension (e.g., my-rule.mdc)
  3. To reference a file in your rule, use the format: [filename.ext](mdc:filename.ext) where the path is relative to the workspace root
  4. Rules use Markdown format with special Cursor-specific extensions
  5. Rules will be shown to the AI to help with codebase navigation and understanding
  6. Metadata is stored in frontmatter and controls how the rule is used and must be formatted properly. Metadata properties are:
  • alwaysApply: true/false # Will apply to every request
  • description: string # A description that allows the agent to fetch the rule
  • globs: string # A comma separated list of gitignore style patterns controlling what files this rule will apply to Usually only one of these types would be set, though it is valid to have globs and a description.

Example rule that is always applied concerning project structure:

---
alwaysApply: true
---
# Project Structure Guide The main entry point is
[index.js](mdc:index.js), which loads configuration from
[config.js](mdc:config.js)

Example rule that only applies to TypeScript and TypeScript React files:

---
globs: *.ts,*.tsx
---
Always use semicolons

Example rule that is manually applied by the user:

---
alwaysApply: false
---
Lots of information about a particular task

You must use these instructions to generate new rules or modify existing ones. Use the conversation history to understand the context of the rule(s) you should generate.

Changes

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.

  1. 2mo ago First seen · 44 lines · 0 tokens per session scan A 1ab5afb8abe0

Subscribe to this mod's changes

generate-rules is a command published in the GitHub repository sfc-gh-abannerjee/SnowGram (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 364 tokens. 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.

Related

generate-rules compared with commands from other repositories

generate-rules next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
generate-rulessfc-gh-abannerjee/SnowGramCommand21mo agoMITA0Claude Code, Cursor
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code