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/albegosu/micrographic-skill/micrographicgit clone --depth 1 https://github.com/albegosu/micrographic-skillWrote 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/albegosu/micrographic-skill/micrographic)<a href="https://agentmods.dev/rules/albegosu/micrographic-skill/micrographic"><img src="https://agentmods.dev/badge/rules/albegosu/micrographic-skill/micrographic.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 | $0.00173 | $0.00173 |
| Opus 5 | $0.00086 | $0.00086 |
| Sonnet 5 | $0.00035 | $0.00035 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
micrographic 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.
What it actually says
When building or styling UI components, pages, dashboards, or design systems, follow the micrographic skill at .cursor/skills/micrographic/SKILL.md.
Trigger when the user mentions micrographic, spec sheet, technical grid, industrial aesthetic, blueprint UI, dense information UI, schematic interface, brutalist typography, or wants UI that feels like product labels, hardware spec sheets, or care tags.
Core constraints: compression not minimalism; metadata as texture; two type scales only (display vs micro); near-monochrome palette with signal accents (orange/red/yellow); schematic geometry (grids, hairlines, corner brackets, dimension lines).
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 · 11 lines · 173 tokens per session scan A 49178e41a484
micrographic is a cursor rule published in the GitHub repository albegosu/micrographic-skill (4 stars, last pushed 3mo ago), licensed MIT. It adds 173 tokens to every session, about $0.0009 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-31.
Other cursor rules, from other repositories
frontend-10x-system
High-signal frontend art direction, system design, and anti-generic guardrails.
frontend
Demo Shop frontend guidance.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
frontend-theme-guidelines
Cursor rule "frontend-theme-guidelines" from KroMiose/nekro-agent, covering 前端主题系统开发指南, 主题系统架构, 核心文件结构, 基本原则 and 主题使用指南.
taste-enforcement
These dials drive all downstream decisions. Adjust per-prompt when the user specifies a different mood.