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/mslavov/shelly-forgeWrote 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/mslavov/shelly-forge/cursor)<a href="https://agentmods.dev/rules/mslavov/shelly-forge/cursor"><img src="https://agentmods.dev/badge/rules/mslavov/shelly-forge/cursor/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/mslavov/shelly-forge/cursor"><img src="https://agentmods.dev/badge/rules/mslavov/shelly-forge/cursor.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.00343 | $0.00343 |
| Opus 5.5 | $0.00137 | $0.00137 |
| Sonnet 5.5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
CURSOR 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 1mo 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
Documentation Usage Guidelines
CRITICAL: Framework-First Reading Order
📚 MANDATORY READING ORDER:
- FIRST: Read rules in @rules/ - Framework rules and development guidelines
- SECOND: Read @INDEX.md - Documentation navigation hub
- THIRD: Read your agent definition in @definitions/ (if applicable)
- THEN: Consult project-specific documentation as needed
Pre-Task Protocol
- Verify you've read the framework rules - All files in @rules/ and @INDEX.md are mandatory
- Review relevant documentation - Use @INDEX.md to find specific docs
- Check the Quick Task Lookup - Find the right documents for your task type
- Read @system-overview.md for system understanding when needed
- Consult product documents from docs/product as needed
- Reference technical docs from docs/tech as needed
Post-Task Protocol
- Update the single authoritative source for any changed information
- Update cross-references if new relationships are created
- Move completed tasks from @tasks/in-progress/ to @tasks/done/
- Update @INDEX.md if new documents are created
Agent Commands
Agent commands are available with @ prefix (e.g., @architect, @developer). Each command:
- Provides a brief role description
- Links to full documentation using Cursor's @ notation
- Assumes this CURSOR.mdc file has been read
See available commands in .cursor/rules/*.mdc
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.
- 1mo ago First seen · 40 lines · 343 tokens per session scan A 7575ade33f49
CURSOR is a cursor rule published in the GitHub repository mslavov/shelly-forge (20 stars, last pushed 1mo ago), licensed MIT. It adds 343 tokens to every session, about $0.0014 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-09-01.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).