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 skills add MrBlushu/blushu-design-skills --skill set-the-gridgit clone --depth 1 https://github.com/MrBlushu/blushu-design-skillsWrote 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/skills/mrblushu/blushu-design-skills/set-the-grid)<a href="https://agentmods.dev/skills/mrblushu/blushu-design-skills/set-the-grid"><img src="https://agentmods.dev/badge/skills/mrblushu/blushu-design-skills/set-the-grid/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/skills/mrblushu/blushu-design-skills/set-the-grid"><img src="https://agentmods.dev/badge/skills/mrblushu/blushu-design-skills/set-the-grid.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.00100 | $0.01991 |
| Opus 5 | $0.00050 | $0.00996 |
| Sonnet 5 | $0.00020 | $0.00398 |
| Haiku 4.5 | $0.00010 | $0.00199 |
Grade A, and why
set-the-grid 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 11d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set the Grid
Establish scope and evidence
Identify the target page, template, component family, or layout system; the content hierarchy; the structural problem; and the requested mode.
- Treat design and review requests as read-only.
- Treat build, change, refactor, implement, or fix requests as authorization for scoped edits.
- Keep product strategy, interaction behavior, aesthetic direction, usability claims, copy, and semantic line breaking outside scope.
- For mixed requests, complete only the structural portion supported by existing decisions and name any required handoff.
- Do not infer grid-system work from a vague request to clean up layout or spacing; require a coordinated structural signal or keep the response to a focused diagnosis.
- Inspect the workspace, current implementation, tokens, handoffs, and rendered evidence before asking for information already available.
- Ask only when missing hierarchy, target containers, or content form would force materially different costly work; otherwise use a reversible labeled assumption.
- Mark evidence as observed, supplied, inferred, assumed, or unverified. Never present placeholder content as evidence.
Choose one operating mode:
- Design: specify the system and verification plan without editing files.
- Revision: diagnose an existing system and propose the smallest coherent correction.
- Implementation: edit the authorized structural surface and verify the rendering.
- Review: report prioritized structural findings without editing.
- Focused decision: answer one bounded question without expanding into a redesign.
Execute only the necessary workflow
Run only the steps needed by the scope. For a focused decision, skip unrelated inventory, candidate derivation, transformation, implementation, and reference loading.
1. Inspect the current system
Locate governing containers, component boundaries, primitives, tokens, queries, offsets, overflow, media wrappers, and DOM or focus order. Render representative states and widths when possible. Distinguish shared rules, justified exceptions, drift, compensation, and unknown behavior.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 137 lines · 100 tokens per session scan A 52995c959dec
set-the-grid is a skill published in the GitHub repository MrBlushu/blushu-design-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 1,991 once invoked, about $0.0005 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 skills, from other repositories
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", or "vs best practices".
design
Use when designing or refreshing a web UI or landing page — visual concept, type/color/spacing/motion tokens, composition, rescuing a UI that reads AI-generic, or a graded design review. Brand-grounded and research-first; ships Tailwind v4 + Next.js 15 under WCAG 2.2 AA and Core Web Vitals budgets. NOT the words on…
webd
Web design workflow for landing pages, SaaS frontends, conversion-oriented pages, and non-generic UI. Use when building or improving a website, landing page, SaaS UI, hero section, pricing page, conversion funnel, shadcn/ui interface, or when the user invokes /webd or @webd.
anti-ui-slop
Stop coding agents from shipping generic UI. Extend the product's design system, use UIZZE evidence only when useful, cover required states, and inspect the rendered result.
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
anti-ui-slop
Stop coding agents from shipping generic UI. Extend the product's design system, use UIZZE evidence only when useful, cover required states, and inspect the rendered result.