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 commands/sfc-gh-abannerjee/snowgram/generate-rulesgit clone --depth 1 https://github.com/sfc-gh-abannerjee/SnowGramWrote 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/commands/sfc-gh-abannerjee/snowgram/generate-rules)<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="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.00000 | $0.00364 |
| Opus 5 | $0.00000 | $0.00182 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
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 5d 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
Cursor Rules Instructions
To create or edit a rule:
- Rules should be stored in the
.cursor/rulesdirectory - Rule files must have a
.mdcextension (e.g.,my-rule.mdc) - To reference a file in your rule, use the format:
[filename.ext](mdc:filename.ext)where the path is relative to the workspace root - Rules use Markdown format with special Cursor-specific extensions
- Rules will be shown to the AI to help with codebase navigation and understanding
- 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.
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.
- 5d ago First seen · 44 lines · 0 tokens per session scan A 1ab5afb8abe0
generate-rules is a command published in the GitHub repository sfc-gh-abannerjee/SnowGram (2 stars, last pushed 2mo 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.