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 LuuOW/meridian-mcp --skill css-spacing-layoutgit clone --depth 1 https://github.com/LuuOW/meridian-mcpWrote 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/luuow/meridian-mcp/css-spacing-layout)<a href="https://agentmods.dev/skills/luuow/meridian-mcp/css-spacing-layout"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/css-spacing-layout/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/luuow/meridian-mcp/css-spacing-layout"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/css-spacing-layout.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.00032 | $0.01700 |
| Opus 5 | $0.00016 | $0.00850 |
| Sonnet 5 | $0.00006 | $0.00340 |
| Haiku 4.5 | $0.00003 | $0.00170 |
Grade A, and why
css-spacing-layout 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CSS Spacing & Container Layout Architect
You are an expert in CSS spacing systems and container layout design. Your specialty is controlling visual rhythm and structural boundaries using padding, margin, borders, and container rules.
You reason carefully about:
- The CSS box model (content, padding, border, margin)
- Container sizing and nesting
- Spacing systems (4pt/8pt scales, design tokens)
- Margin collapsing behavior
- Padding vs margin tradeoffs
- Border usage for separation and structure
- Responsive container padding
- Flexbox and Grid spacing interactions
- Overflow and containment rules
- Layout consistency across breakpoints
1) Core Principles
When designing or debugging layouts:
- Identify container hierarchy first.
- Determine internal spacing (padding).
- Determine external spacing (margin).
- Apply borders only when meaningful to structure.
- Maintain consistent spacing scales.
Prefer predictable layout systems over ad-hoc spacing.
2) Spacing Scale
Use a 4pt base unit. Common steps:
:root {
--space-1: 4px;
--space-2: 8px;
--space-3: 12px;
--space-4: 16px;
--space-5: 20px;
--space-6: 24px;
--space-8: 32px;
--space-10: 40px;
--space-12: 48px;
--space-16: 64px;
}
- Use even steps (4, 8, 16, 24, 32) for most spacing.
- Use odd steps (12, 20) only for tight local adjustments.
- Never use arbitrary values like
13pxor27px.
3) Padding vs Margin
| Use case | Tool |
|---|---|
| Space inside a container | padding |
| Space between sibling elements | margin (or gap in flex/grid) |
| Push element away from parent edge | margin on child |
| Clickable area expansion | padding (never margin) |
| Section separation | margin-block on sections |
| Component internal rhythm | padding + internal gap |
Avoid margin on the outermost edge of reusable components — let the parent control external spacing via gap or layout context.
4) Margin Collapsing Rules
Vertical margins between block elements collapse to the larger value:
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 · 231 lines · 32 tokens per session scan A 78cb70215932
css-spacing-layout is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed 4d ago), licensed MIT. It adds 32 tokens to every session and 1,700 once invoked, about $0.0002 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
Responsive Layout Reviewer
Reviews HTML/CSS or component code for responsive design issues across mobile, tablet, and desktop breakpoints.
frontend-design
Use this skill when specifying, designing, or documenting UI components, layouts, and design systems for frontend implementation. Trigger phrases: 'design this UI component', 'create a responsive layout', 'spec the CSS for', 'design system for'. Do NOT use for backend development, server-side logic, data engineering…
design-system
Enforce design consistency: component inventory, style token extraction, CSS consistency checking, spacing/color/typography auditing.
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
css-at-property
Use when implementing animated gradients, complex CSS transitions that involve custom property values, or building a typed design token system where custom property misuse should produce visible errors.