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/Kevin-Liu-01/Agent-MachinesWrote 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/kevin-liu-01/agent-machines/reticle-grid-pattern)<a href="https://agentmods.dev/rules/kevin-liu-01/agent-machines/reticle-grid-pattern"><img src="https://agentmods.dev/badge/rules/kevin-liu-01/agent-machines/reticle-grid-pattern.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.1 | $0.00000 | $0.01370 |
| Opus 5 | $0.00000 | $0.00685 |
| Sonnet 5 | $0.00000 | $0.00274 |
| Haiku 4.5 | $0.00000 | $0.00137 |
Grade A, and why
reticle-grid-pattern 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reticle Grid Pattern
The canonical layout system for Agent Machines landing sections. Every section is a structural grid of hoverable cells with hairline borders, rounded cards inside cells, full-width separator lines, and hatched margins.
Page-level structure
[outer] [gutter 4rem] [hatch margin 4rem] [content max-w] [hatch margin 4rem] [gutter 4rem] [outer]
- Content: centered, capped at
--ret-content-max(1200px). - Margins:
--ret-rail-offset(4rem) wide, filled with 45deg hatch (repeating-linear-gradient(45deg, var(--ret-rail) 0 1px, transparent 1px 6px)). - Gutters: same width as margins, empty, bordered on their inner edge.
- Page root has
overflow-x-hiddento clip full-bleed hairlines.
Grid construction
Sections use CSS Grid with a narrow auto-width left column + N equal columns:
<div className="grid grid-cols-4 auto-rows-auto md:grid-cols-[auto_repeat(8,1fr)]">
- Column 1 (
auto): narrow rail for navigation/tool icons. - Columns 2–9 (
1freach): content cells. - Mobile collapses to
grid-cols-4, hiding rail and rightmost cells.
Cell anatomy
Every cell uses the Cell component:
<Cell action="..." agent={agent} hue={hue} className="..." hoverVisual={...}>
{children}
</Cell>
- Borders:
border-b border-r border-[var(--ret-border)]— hairline on bottom and right. Last column in a row gets!border-r-0. Last row gets!border-b-0. This prevents doubled borders at edges. - Hover: every cell (including empty ones) has a hover overlay with:
- A visual effect (
HoverHatch,HoverGlow,HoverPulseGrid,HoverScene,HoverGradient). - An agent action label (logo + monospaced text + pulsing dot) in the bottom-left corner, colored in the active agent's hue.
- A visual effect (
Cards inside cells
Content cells contain a rounded card with padding:
<Cell ...>
<div className="h-full p-1.5">
<div className="h-full rounded-lg border border-[var(--ret-border)] bg-[var(--ret-bg)]">
{/* content */}
</div>
</div>
</Cell>
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 · 143 lines · 0 tokens per session scan A e308f83c0112
reticle-grid-pattern is a cursor rule published in the GitHub repository Kevin-Liu-01/Agent-Machines (26 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,370 tokens. 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-30.
Other cursor rules, from other repositories
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
ui-motion-workflow
Orchestrate motion-aware UI work by sequencing direction, provider choice, implementation, and browser validation.
accessibility
Rules for ensuring accessibility in Astro components, including semantic HTML and ARIA attributes.
quasar_fixes
A Quasar interface rule requiring extra SCSS fixes when using q-scroll-area or q-tooltip, including a fix for iOS scaling.
nextjs-app-router
Next.js 14+ App Router Standards.
7-day-nextjs-web-design-cursor
A seven-day design workflow for web products that will be built in Next.js.