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.00054 | $0.01847 |
| Opus 5 | $0.00027 | $0.00924 |
| Sonnet 5 | $0.00011 | $0.00369 |
| Haiku 4.5 | $0.00005 | $0.00185 |
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 3d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Style
OrchestKit leans into ASCII art and semantic emojis for visual scanability — but only with a fixed vocabulary, only where they earn their keep, and never where they break greppability, byte budgets, or accessibility.
The Twelve-Glyph Vocabulary
Every emoji must come from this list. No decorative additions. Adding to the list requires a PR.
| Glyph | Meaning | Use for |
|---|---|---|
| ✅ | success / done / pass | completed tasks, passing tests, met criteria |
| ❌ | failure / blocked / no | failed tests, denied actions, explicit "don't" |
| ⚠️ | warning / caution | non-fatal issues, edge cases, soft constraints |
| 🔄 | in-progress / loop | running tasks, retry loops, async work |
| ⏸ | paused / blocked-by | waiting on dependency or user input |
| 💡 | hint / suggestion | optional improvements, "consider this" |
| 🚨 | hard block / critical | security violations, hook denies, must-fix |
| 🎯 | goal / target | objectives, success criteria, focus |
| 🔥 | high-leverage / hot | top priority, recommended path |
| 📜 | docs / skill / spec | references to SKILL.md, documentation |
| 🤖 | agent | references to subagents |
| ⚡ | hook | references to hooks, fast/automated paths |
Risk and ranking glyphs (always paired, never solo):
- Risk: 🟢 low · 🟡 medium · 🔴 high
- Ranking: 🥇 1st · 🥈 2nd · 🥉 3rd
ASCII Palette
Use these character sets only — keeps rendering predictable across terminals, GitHub, and CI logs.
Box drawing: ┌─┐ │ ┘─└ (light)
╔═╗ ║ ╝═╚ (heavy — reserve for top-level section headers)
Dividers: ─── ═══
Arrows: → ↓ ▶ ◀
Progress: ▓▓▓░░ ████████░░
Bullets: • ◦ ‣
Do not use: 3D box characters, shaded blocks for decoration, ASCII-art logos, or any character that requires a non-default monospace font.
Per-Surface Rules
✅ Assistant chat output (BUDGETED)
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.
- 3d 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 (264 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,847 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-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.
components
Rules for component usage - which component libraries are allowed (shadcn/ui, Aceternity, Kibo, Magic UI, etc.), reuse over recreation, table implementation standards, and component modularization for both new features and existing 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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.