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/markerikson/opencode-config-example/dashboard-designnpx skills add markerikson/opencode-config-example --skill dashboard-designgit clone --depth 1 https://github.com/markerikson/opencode-config-exampleWhat 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.00044 | $0.03151 |
| Opus 5 | $0.00022 | $0.01576 |
| Sonnet 5 | $0.00009 | $0.00630 |
| Haiku 4.5 | $0.00004 | $0.00315 |
Grade A, and why
dashboard-design 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 2d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dashboard Design Patterns
Focused design guidance for data-dense dashboard UIs — trading dashboards, analytics panels, code review tools, monitoring interfaces. Complements general frontend design skills with patterns specific to tabular data, charts, status indicators, and dark-theme-first development.
Data Tables
Numeric Formatting
- Use
font-variant-numeric: tabular-numson ALL number columns — prices, quantities, percentages, scores. Without this, columns jitter as values change. - Right-align numeric columns, left-align text columns. This is not optional — it's how humans scan numbers.
- Format consistently: if one price shows
$1,234.56, all prices show two decimal places. Don't mix$5and$5.00.
Column Layout
- Use
table-layout: fixedwith<colgroup>for consistent column widths. Auto-layout causes content-dependent jitter. - Define minimum column widths so narrow data doesn't collapse columns to unreadable sizes.
- Consider sticky first column (symbol/name) on horizontally scrollable tables.
Row Differentiation
- Use ONE technique: subtle alternating backgrounds OR increased row spacing — not both. Both together creates visual noise.
- Alternating backgrounds: keep contrast extremely subtle (2-3% lightness difference). The goal is a guide rail for the eye, not a zebra.
- Add a hover highlight row to help track across wide tables.
- Every row looking identical is a hierarchy problem — use font-weight on the primary column (bold for Symbol, normal for secondary data).
Sortable Columns
- Active sort column needs a clear indicator (arrow icon + subtle column highlight).
- Inactive sortable columns: show a muted indicator on hover only.
- Multi-sort: show sort priority numbers if supported.
Empty & Missing Data
- Empty cells: use em-dash (—) styled muted (
color: var(--color-text-tertiary)) — never leave cells blank (blank looks like a rendering bug). - When MOST cells in a column are empty, that's a data/design problem: consider hiding the column, showing a summary row, or collapsing to a denser layout.
- Distinguish between "no value" (—), "zero" (0), and "not applicable" (n/a).
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.
- 2d ago First seen · 307 lines · 44 tokens per session scan A acdf3b14778a
dashboard-design is a skill published in the GitHub repository markerikson/opencode-config-example (44 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 3,151 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…