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 NOMARJ/sigil --skill dashboard-patternsgit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/dashboard-patterns)<a href="https://agentmods.dev/skills/nomarj/sigil/dashboard-patterns"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/dashboard-patterns/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/nomarj/sigil/dashboard-patterns"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/dashboard-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00140 | $0.02492 |
| Opus 5.5 | $0.00056 | $0.00997 |
| Sonnet 5.5 | $0.00028 | $0.00498 |
| Haiku 4.5 | $0.00014 | $0.00249 |
Grade A, and why
dashboard-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dashboard Patterns
Tactical rules for building dashboards that communicate data clearly. These patterns come from eye-tracking research, information design principles, and proven UX heuristics. Apply them before reaching for any styling decisions.
1. Scan Path Patterns
Choose your layout based on who's reading and what they need.
Z Pattern
Eye scans: top-left → top-right → diagonal down → bottom-left → bottom-right.
- Use for: Executive dashboards, overview/summary views, status boards.
- Rule: Place #1 KPI top-left, #2 KPI top-right. Supporting detail bottom half.
- Anti-pattern: Burying the most important metric in the middle or bottom.
F Pattern
Eye scans: full top row → shorter second row → drops straight down the left edge.
- Use for: Analytical dashboards, data-heavy views, list-driven UIs.
- Rule: Put #1 metric at the top. Each row below gets progressively less attention. Front-load labels and key values on the left side.
- Anti-pattern: Placing critical filters or actions on the right side where attention drops off.
Selection guide
| Audience | Dashboard type | Pattern |
|---|---|---|
| C-suite / board | Status overview | Z |
| Analysts / ops | Deep-dive, investigation | F |
| Mixed | Summary + drill-down | Z top section, F below fold |
2. Layout Composition
60/40 Split
Give the primary visual (main chart, map, key table) 60% width. Secondary content gets 40%. Eyes gravitate to the larger area. Simple rule, big impact on visual balance.
Golden Ratio Grid
For complex dashboards with 6+ widgets: use a 3-column grid where the left column is ~38%, middle ~38%, right ~24%. Or 2-column with 62/38 split. Feels balanced without being rigid.
Card Hierarchy
Not all cards are equal. Signal importance through:
- Size: Important metrics get larger cards.
- Elevation: Higher shadow = higher importance (use sparingly — max 2 levels).
- Position: Top-left is prime real estate. Bottom-right is the graveyard.
- Border/accent: A left-border color accent on a card draws the eye without shouting.
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 · 211 lines · 140 tokens per session scan A 3664c9b48da2
dashboard-patterns is a skill published in the GitHub repository NOMARJ/sigil (6 stars, last pushed 11d ago), licensed Apache-2.0. It adds 140 tokens to every session and 2,492 once invoked, about $0.0006 per session on Opus 5.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
bb-theme-authoring
Create or edit BB color themes and inspect them in the Theme Preview panel.
agent-annotations
Create or edit element annotations in desktop Browser tabs, or update saved annotation comments through the plugin RPC.
use-show-pages
Build, inspect, update, restore, or share Avibe Show Pages for visual explanations, diagrams, reports, or interactive prototypes. Covers the page workspace and its Git history.
make-a-screen
Use when an answer about the connected product would land better as something the person can look at and use than as text you type out — a comparison, a trend, many rows, a thing they will come back to, or a thing they need to act on. Also use when they ask to change a screen they already have.
qa-design
UI/UX design audit and verification of web best practices, including responsive/mobile-first breakpoints. Trigger when the user wants to audit the design, verify the UI/UX, check responsive behaviour, or improve the user interface.
dev-frontend-design
Distinctive UI design with strong art direction. Trigger when the user wants to create an interface, a landing page, a visual component, or when frontend code creation is detected without a defined design direction.