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/thatrebeccarae/claude-marketingWrote 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/thatrebeccarae/claude-marketing/tech-diagram)<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/tech-diagram"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/tech-diagram.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.00053 | $0.01023 |
| Opus 5 | $0.00026 | $0.00511 |
| Sonnet 5 | $0.00011 | $0.00205 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
tech-diagram 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Diagram Generator
Generate technical architecture diagrams and system illustrations as standalone HTML files with embedded CSS + inline SVG. No external dependencies.
Core Capabilities
- Pipeline flow diagrams (data pipelines, CI/CD, ETL)
- Layer/stack diagrams (tech stack, OSI model, infrastructure)
- Component diagrams (microservices, system architecture)
- Before/after split comparisons
- Timeline diagrams (roadmaps, migration phases)
- Metric callout rows (KPI summaries)
Design System
Color Tokens
:root {
/* Dark mode (default canvas) */
--bg-deep: #0d1117;
--bg-surface: #161b22;
--bg-elevated: #21262d;
--border-subtle: rgba(240, 246, 252, 0.1);
--text-bright: #f0f6fc;
--text-secondary: #8b949e;
--text-muted: #6e7681;
/* Accent palette */
--accent-blue: #58a6ff;
--accent-green: #3fb950;
--accent-purple: #bc8cff;
--accent-orange: #d29922;
--accent-red: #f85149;
--accent-cyan: #39d2c0;
--accent-pink: #f778ba;
/* Light mode (optional, for embedded diagrams) */
--bg-light: #ffffff;
--bg-light-surface: #f6f8fa;
--text-light-primary: #1f2328;
--text-light-secondary: #656d76;
}
Color Rules
- Dark mode is default for all diagrams
- Each pipeline stage or layer gets a distinct accent color
- Use
--text-secondaryfor labels and annotations - Use
--border-subtlefor connecting lines and borders - Semantic colors: green = healthy/success, red = error/alert, orange = warning
Typography
| Role | Font | Weight | Size |
|---|---|---|---|
| Diagram title | system-ui | 600 | 28-32px |
| Section/stage label | system-ui | 600 | 16-18px |
| Description text | system-ui | 400 | 13-14px |
| Annotation | monospace | 400 | 12px |
| Metric value | monospace | 700 | 36-48px |
Canvas
Width: 1200px (default, responsive down to 800px)
Height: auto (content-driven)
Padding: 48px
Component Library
Pipeline Flow
Horizontal or vertical sequence of stages with connecting arrows. Each stage has an icon area, label, and description.
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.
- 8d ago First seen · 127 lines · 53 tokens per session scan A af9da3a9ada8
tech-diagram is a cursor rule published in the GitHub repository thatrebeccarae/claude-marketing (132 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 1,023 once invoked, about $0.0003 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
svg-check
Apply when editing, generating, or reviewing any SVG diagram. Pixel-perfect Playwright bbox-check is the acceptance test — eyeballing is not sufficient. Run on every SVG before declaring done.
diagrammer
Author Diagrammer JSON for the Diagrammer viewer. Use whenever the user asks for a mind map, concept map, flowchart, tree, dependency graph, ER diagram, or timeline. Output a single JSON document conforming to the schema below.
drawio
Apply when creating or reviewing architecture diagrams, Mermaid diagrams, or draw.io files.
settings-page
Settings page layout, tabs, Preferences section, AI Setup section, auto-save pattern, custom UI components.
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.