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/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/visual-style)<a href="https://agentmods.dev/rules/yonatangross/orchestkit/visual-style"><img src="https://agentmods.dev/badge/rules/yonatangross/orchestkit/visual-style/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/yonatangross/orchestkit/visual-style"><img src="https://agentmods.dev/badge/rules/yonatangross/orchestkit/visual-style.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.00029 | $0.02760 |
| Opus 5.5 | $0.00012 | $0.01104 |
| Sonnet 5.5 | $0.00006 | $0.00552 |
| Haiku 4.5 | $0.00003 | $0.00276 |
Grade A, and why
visual-style 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 20d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Style in Chat (glyph renders, one per reply, up to ~50 lines)
Reset 2026-09-17 by operator word after seeing a peer's disk-cleanup render: "we don't use it enough, ASCII and emoji art in chat in general". This supersedes the 2026-08-09 budget (12 lines, 40 percent), which had swung too far the other way: replies answered shape-shaped questions in prose and one thin table.
The three rules
- An answer with shape gets a render. Status, inventories, audits, budgets, comparisons, rankings, pipelines, "what is using X", "where do we stand". A single fact, a definition, or a one-line ask gets prose only.
- Verdict first, then the render, then what the numbers told me. One prose line states the point before the render. After the render, two or three bold-led bullets say what is not obvious from the chart. If the reader has to parse the render to learn the verdict, the reply failed.
- One render, up to about 50 lines, 76 cells wide. Two competing renders in one reply is flooding. Above 50 lines it is a page: write the HTML or markdown, print the URL or path, keep a 10-line excerpt in chat.
Anatomy of a render (the reference shape)
🖥️ MACINTOSH HD · /System/Volumes/Data
[▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░]
used 355 G free 73 G 83 % full · 460 G total
────────────────────────────────────────────────
🟢 SAFE, pure caches; nothing lost, tools refill them
────────────────────────────────────────────────
🐳 Docker dangling images+build cache ▓▓▓▓░░░ 14.5 G docker prune
🌐 Chrome caches (Google + Island) ▓▓░░░░░ 8.9 G browsers refill
📦 npm cache ~/.npm ▓▓░░░░░ 6.2 G npm cache clean
── 45.3 G
🟢 safe 45 G + 🟡 regenerable 41 G ≈ 87 G → free 73 G → ~159 G
ℹ️ Docker.raw shows 432 G but is sparse: 37 G real. Prune shrinks it.
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.
- 20d ago Changed · +1 lines 529704a5eee9
- 1mo ago Changed · +2 lines e022e7407305
- 1mo ago Changed · +96 lines · -25 tokens per session 21a2d2be9853
- 1mo ago First seen · 145 lines · 54 tokens per session scan A 529492f68ce2
visual-style is a cursor rule published in the GitHub repository yonatangross/orchestkit (298 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 2,760 once invoked, about $0.0001 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-09.
Other cursor rules, from other repositories
pn-design-system
Design system rule: enforces token usage when editing CSS, SCSS, or styled components. Use tokens for color, spacing, typography; avoid one-off values. For establishing or auditing a design system, use the pn-design-system skill.
pn-figma
Figma design-to-code conventions: token extraction, component mapping, naming alignment. Use when implementing designs from Figma or maintaining design-code sync.
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.