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 skills/nomarj/sigil/dashboard-patternsnpx 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.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 | $0.00140 | $0.02492 |
| Opus 5 | $0.00070 | $0.01246 |
| Sonnet 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 3d 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.
- 3d ago First seen · 211 lines · 140 tokens per session scan A 3664c9b48da2
dashboard-patterns is a skill published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 140 tokens to every session and 2,492 once invoked, about $0.0007 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
sftp-cc
通用 SFTP 上传工具，通过自然语言触发，将本地项目文件上传到远程服务器。支持增量上传、私钥自动绑定与权限修正。.
workflows
Execute a workflow script that orchestrates multiple subagents deterministically. Use when the user explicitly requests a workflow, multi-agent orchestration, parallel or sequential agent pipelines, structured agent outputs, or a durable background workflow run.
devtools-event-client
Create typed EventClient for a library. Define event maps with typed payloads, pluginId auto-prepend namespacing, emit()/on()/onAll()/onAllPluginEvents() API. Connection lifecycle (5 retries, 300ms), event queuing, enabled/disabled state, SSR fallbacks, singleton pattern. Unique pluginId requirement to avoid event…
genbench
Run Vendo's buy-vs-build generation benchmark — generation time + accuracy of the real Vendo pipeline vs raw-Claude baselines (diy, claude-code) on JSON-defined worlds. Use when asked to benchmark generation, compare Vendo vs raw models, measure generation speed/cost, or add genbench worlds/cases.
jk
Jenkins CLI for controllers. Use when users need to manage jobs, pipelines, config.xml, runs, logs, artifacts, credentials, nodes, or queues in Jenkins. Triggers include "jenkins", "jk", "pipeline", "build", "job create", "job config", "config.xml", "run logs", "jenkins credentials", "jenkins node".
orch
AI agent orchestrator — manage teams of AI agents that work on your codebase in parallel. Use when the user wants to: run multiple agents, coordinate AI work, deploy agent teams, manage tasks/goals/agents, check orchestrator status, or mentions 'orch', 'orchestry', 'agents team', 'agent orchestration'.