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 commands/adityaraj0421/naksha-studio/dashboard-layoutgit clone --depth 1 https://github.com/Adityaraj0421/naksha-studioWrote 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/commands/adityaraj0421/naksha-studio/dashboard-layout)<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/dashboard-layout"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/dashboard-layout.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.00037 | $0.01629 |
| Opus 5 | $0.00018 | $0.00814 |
| Sonnet 5 | $0.00007 | $0.00326 |
| Haiku 4.5 | $0.00004 | $0.00163 |
Grade A, and why
dashboard-layout 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 5d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dashboard-layout
Design a complete dashboard: sidebar navigation, KPI row, chart areas, filter bar, and data tables. Outputs production-ready HTML/CSS with responsive behavior and dark mode support.
Usage: /dashboard-layout <description>
Examples:
/dashboard-layout SaaS analytics dashboard with MRR, churn, active users/dashboard-layout e-commerce admin: orders, revenue, inventory, customer table/dashboard-layout monitoring dashboard for API performance metrics --style dark-tech/dashboard-layout --type executive weekly business review for C-suite
Process
1. Parse the Request
Extract from $ARGUMENTS:
- Dashboard type: analytics | operational | executive | admin | reporting | monitoring
- Domain: SaaS, e-commerce, fintech, healthcare, engineering, marketing, etc.
- KPI metrics: Extract 3–6 headline metrics from the description
- Style:
--style dark-tech(default for monitoring),--style minimal,--style corporate - Type flag:
--type executiveadjusts information density and layout - Dark flag:
--darkrenders dark-first
2. Select Dashboard Pattern
Apply the dashboard type pattern from the Dashboard Architect reference:
| Type | Primary layout | Density | Key emphasis |
|---|---|---|---|
| analytics | Sidebar + wide charts + KPI row | Medium | Time-series charts, period comparison |
| operational | Dense grid + real-time indicators | High | Status badges, alert log, gauges |
| executive | Spacious, large typography | Low | Headline KPIs, sparklines, trend arrows |
| admin | Table-heavy + sidebar | High | CRUD tables, filters, bulk actions |
| monitoring | Full-width timeline + alert panel | High | Color-coded status, incident feed |
3. Define Information Hierarchy
Establish the three-level hierarchy:
Level 1 — KPI Cards (top): 3–5 metrics that answer the core question
- For each KPI: label, current value, unit, trend vs previous period, optional sparkline
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.
- 5d ago First seen · 190 lines · 37 tokens per session scan A ae1296f3ecbb
dashboard-layout is a command published in the GitHub repository Adityaraj0421/naksha-studio (316 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 1,629 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 commands, from other repositories
theme-swap
Recolour an extracted site's design around a new brand primary. OKLCH hue rotation preserves perceptual lightness — neutrals, type, spacing, and motion stay untouched. Side-by-side HTML preview + recoloured tokens (DTCG, Tailwind, shadcn, Figma).
remix
Restyle a site in another design vocabulary — brutalist, swiss, art-deco, cyberpunk, soft-ui, or editorial. Preserves page shape, swaps the visual vocabulary.
studio
Launch the local design Studio — a live token editor over the latest extraction. Edit, preview a wall of real components, toggle dark mode, inspect motion, and export.
full-diagnostic
Comprehensive design system health sweep.
describe-component
Generate an AI-optimised component description.
docs-coverage
Audit whether your documentation surface keeps pace with your components.