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 rules/brunogama/ios-cursor-rules/visualization-rulegit clone --depth 1 https://github.com/brunogama/ios-cursor-rulesWhat 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 | $0.00810 | $0.00810 |
| Opus 5 | $0.00405 | $0.00405 |
| Sonnet 5 | $0.00162 | $0.00162 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
visualization-rule 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 2d 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
Visualization System
Rule for generating visual representations of project elements to improve understanding and communication.
actions:
-
type: react conditions:
- pattern: "visualize specs|diagram specs" action: |
Generate specification visualization
I'll create a visual representation of project specifications:
- Generate a dependency diagram showing relationships between specs
- Create a completion heatmap showing progress across domains
- Visualize requirement distribution and completion status
- Show timeline of specification development
The visualization will use SVG or Mermaid diagrams for easy rendering.
-
type: react conditions:
- pattern: "visualize tasks|diagram tasks" action: |
Generate task visualization
I'll create a visual representation of project tasks:
- Generate a Gantt chart of tasks with timelines
- Create a kanban-style board visualization showing task status
- Show task dependencies and critical paths
- Visualize task distribution across domains
This provides a quick visual overview of project progress.
-
type: react conditions:
- pattern: "visualize knowledge|diagram knowledge" action: |
Generate knowledge visualization
I'll create a visual representation of the knowledge base:
- Generate a knowledge map showing relationships between learnings
- Create category distribution charts
- Show knowledge growth over time
- Visualize knowledge clusters and gaps
This helps identify patterns and relationships in captured knowledge.
-
type: react conditions:
- pattern: "visualize architecture|diagram architecture" action: |
Generate architecture visualization
I'll create a visual representation of the project architecture:
- Generate component diagrams showing system structure
- Create sequence diagrams for key workflows
- Visualize data flow between components
- Show dependency relationships
This provides a clear visual understanding of system design.
-
type: react event: "task_summary" action: |
Automatically include task visualizations in summaries
When generating task summaries, I'll include:
- Visual progress indicators
- Timeline charts of task completion
- Distribution visualizations by category
- Burndown/burnup charts
This adds visual context to textual reports.
-
type: suggest message: |
Visualization System
I can create visual representations of project elements:
Commands:
visualize specs- Create specification relationship and progress diagramsvisualize tasks- Generate task timelines and status visualizationsvisualize knowledge- Create knowledge maps and category chartsvisualize architecture- Generate system architecture diagrams
Automatic Behaviors:
- When generating reports → Include relevant visualizations
- When summarizing status → Add visual progress indicators
Visualizations use SVG or Mermaid diagrams and can be exported for documentation.
examples:
-
input: | visualize specs output: "Generated specification visualization showing relationships and completion status across 24 specifications."
-
input: | visualize architecture output: "Created architecture diagram showing 5 core components and their interactions."
metadata: priority: high version: 1.0
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.
- 2d ago First seen · 130 lines · 810 tokens per session scan A 24556cbedf81
visualization-rule is a cursor rule published in the GitHub repository brunogama/ios-cursor-rules (74 stars, last pushed 1y ago), licensed MIT. It adds 810 tokens to every session, about $0.0040 per session on Opus 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-30.
Other cursor rules, from other repositories
swiftui
Rules for IcySky, a SwiftUI project for a bluesky client.
202-swift-standards-detailed
Swift 6.2 + iOS 18-26 编码规范 - 详细参考.
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.