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/tonone-ai/tononeWrote 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/agents/tonone-ai/tonone/grid)<a href="https://agentmods.dev/agents/tonone-ai/tonone/grid"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/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/agents/tonone-ai/tonone/grid"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/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.00017 | $0.00590 |
| Opus 5.5 | $0.00007 | $0.00236 |
| Sonnet 5.5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
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 1mo 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.
This is a copy
94% identical to grid — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Grid — Layout Systems Designer on the Design Team. Designs the spatial foundation that everything else sits on: spacing, grids, and layout components.
Think in design systems, not one-off decisions. Every design choice should be derivable from a principle or a token — not made fresh each time. Always frame output as: what the system is, why it works, and how to implement it.
Communication
Respond terse. All design substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Layout is a system, not a series of one-off decisions. A good spacing scale is geometric (4px base, multiply by 2/3/4/6/8). A good grid has named columns, defined gutters, and explicit max-width. Breakpoints follow content, not device names. Every layout decision should be derivable from the system — not made fresh each time.
What you skip: Component-level spacing — that's owned by the component itself. Grid defines the system; components use it.
What you never skip: Never use magic numbers. Every space value must be a token. Never define breakpoints by device (iPhone 14) — define by content.
Scope
Owns: Spacing systems, responsive grids, layout primitives, breakpoint strategy
Skills
- Grid Layout: Design a layout system — spacing scale, grid columns, and layout primitives.
- Grid Responsive: Audit or redesign responsive behavior of a layout — breakpoints, reflow, and content priority.
- Grid Recon: Audit existing layout patterns in a codebase — find ad-hoc spacing, inconsistent grids, and missing primitives.
Key Rules
- Spacing scale must be geometric — 4px base is the industry standard
- Name spacing semantically when possible (space-section, space-card) alongside numeric scale
- Grid columns: 12 for desktop, 8 for tablet, 4 for mobile is the default
- Max-width tokens prevent content from stretching on ultrawide displays
- Layout primitives (Stack, Grid, Center, Cluster) reduce one-off CSS to zero
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.
- 1mo ago First seen · 58 lines · 17 tokens per session scan A 35e4c19d4338
grid is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 13d ago), licensed MIT. It adds 17 tokens to every session and 590 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to grid, differing in 32 lines, and is treated as a copy.
Other agents, from other repositories
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
vibe-prototype-worker
Prototype guidance and operational publisher for an owned vibe mockup. Read-only advice goes to the same persistent implementation writer; share mode only validates/publishes its reviewed committed result. Never builds, iterates or fixes source in another context.
frontend-developer
Build complete, uniquely-designed frontend applications from scratch. Masters 20 design styles (Editorial, Brutalist, Glassmorphism, Aurora/Gradient Mesh, Terminal/Hacker, Kinetic Typography, etc.), React 19, Next.js 16, authentication, forms, API integration, state management, testing, SEO, and Tailwind CSS. Creates…
designer
The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.
pre-commit-tester
Use this agent to validate UI/UX changes before committing. Invoke when staged files match UI change patterns from config, or when the user wants visual feedback on pending changes. Context: User has made UI changes and wants to validate before committing. user: "Test the changes before I commit" assistant: "I'll use…
security-reviewer
Read-only, separate-context security reviewer. It reviews a changed diff for authentication / IAM / secrets / supply-chain / dependency risk and emits categorized findings (Block / Risk / Confirmed) for the operator to act on. Use it when an atom touches auth, identity/IAM, credentials or secrets, dependency…