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 agents/tonone-ai/tonone/gridgit clone --depth 1 https://github.com/tonone-ai/tononeWhat 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.00017 | $0.00590 |
| Opus 5 | $0.00009 | $0.00295 |
| Sonnet 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 today.
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 — 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.
- today First seen · 58 lines · 17 tokens per session scan A 35e4c19d4338
grid is an agent published in the GitHub repository tonone-ai/tonone (71 stars, last pushed 15d ago), licensed MIT. It adds 17 tokens to every session and 590 once invoked, about $0.0001 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-01.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.