agentmods.dev

scaffold-dashboard

scaffold-dashboard is a skill for Claude Code from ahpxex/open-dashboard. It costs 82 tokens per session (1,078 once invoked), scanned A, original, MIT.

A clean foundation for a dashboard application, including navigation, forms, tables, charts, sign-in, themes, and data connections. It runs with temporary in-memory data by default and can use Drizzle with Postgres when a database is configured.

In plain words
What is it for?
Use it as the starting point for a back-office app, then add data resources and screens such as tables, forms, charts, or detail views.
Why use it?
It gives a new dashboard a runnable structure before product-specific screens are added. Developers can build and preview the interface without first setting up a database.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash .claude/skills/scaffold-dashboard/scaffold.sh <target-dir>.

Part of the open-dashboard plugin — 4 skills shipped together

not rated 139repo +1 2mo ago A scan SkillSpector: pass 82 tokens original MIT

Good fit Use it as the starting point for a back-office app, then add data resources and screens such as tables, forms, charts, or detail views.

Compare 6 skills from other repositories ↓
View source ↗ ahpxex/open-dashboard open-dashboard.ctxflow.workers.dev
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/ahpxex/open-dashboard
agentmods
npx agentmods add skills/ahpxex/open-dashboard/scaffold-dashboard

Made for: Claude Code.

Or install open-dashboard, the plugin that ships this one along with the rest of its 4 skills.

Wrote 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.

agentmods badge for scaffold-dashboard

README.md
[![agentmods](https://agentmods.dev/badge/skills/ahpxex/open-dashboard/scaffold-dashboard/github.svg)](https://agentmods.dev/skills/ahpxex/open-dashboard/scaffold-dashboard)
Your own site
<a href="https://agentmods.dev/skills/ahpxex/open-dashboard/scaffold-dashboard"><img src="https://agentmods.dev/badge/skills/ahpxex/open-dashboard/scaffold-dashboard/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.

agentmods 80×15 button for scaffold-dashboard

Your own site · 80×15
<a href="https://agentmods.dev/skills/ahpxex/open-dashboard/scaffold-dashboard"><img src="https://agentmods.dev/badge/skills/ahpxex/open-dashboard/scaffold-dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,078 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00082 $0.01078
Opus 5 $0.00041 $0.00539
Sonnet 5 $0.00016 $0.00216
Haiku 4.5 $0.00008 $0.00108

Measured 9d ago against content hash 53da302f4236, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

scaffold-dashboard 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 9d ago.

The scan reads SKILL.md. This mod also ships 7 executable files (base/drizzle.config.ts, base/scripts/create-resource.ts, base/scripts/seed.ts, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/scaffold-dashboard/SKILL.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Scaffold the dashboard foundation

The whole foundation is bundled at base/ — a clean, runnable app shell with no demo content. Materialize it into a new project, then add screens from the add-component catalogue's shapes (and the add-backend operation skill). You don't read the foundation code — you scaffold it.

Scaffold

bash .claude/skills/scaffold-dashboard/scaffold.sh <target-dir>

Copies base/ → target and runs bun install. Then:

cd <target-dir>
bun run dev          # zero-config: in-memory auth + data, no Postgres/Docker

Open it, click Dev quick login ([email protected] / password) → an empty, branded dashboard.

What you get

TanStack Start + Router + Query + Table; shadcn-on-@base-ui/react primitives; Tailwind v4 theme; the form system (TanStack Form + zod); chart components; the Repository data layer (in-memory by default, Drizzle/Postgres when DATABASE_URL is set); better-auth behind the AuthProvider seam; toast + useConfirm; and the auth-guarded routing shell. Rebrand via src/config/app.ts (or the rebrand skill).

Compose a coherent product (not a demo dump)

You are building a real back-office for a specific domain — not showcasing the catalogue. The fastest way to ship something that reads as a patchwork demo is to copy a pile of gallery shapes into the nav. Don't. Instead:

  • The home is an overview, never the placeholder. Replace src/routes/_app/index.tsx (the "clean shell" welcome) with a real overview via add-chart-page — KPIs + charts derived from your actual resources. Shipping the scaffold welcome as the product home is the #1 tell of a demo.
  • Nav = real product sections only: Overview, your resources, Settings. The scaffold base ships clean (no demo resources, no Skills Gallery) — you add product sections to src/lib/sidebar-items.ts, you don't prune sample ones.
  • Pick the archetype that fits each resource's shape, don't add one of each: flat list → CRUD table (add-backend); rich record → + add-detail-page; an inbox you triage → add-master-detail; a staged pipeline → add-kanban; people/visual items → add-card-list; date-bound items → add-calendar; metrics → add-chart-page.
  • Every nav item gets a distinct, meaningful Phosphor icon — never repeat one icon (e.g. SquaresFourIcon) down the list.
  • Use product language. Labels and page copy name the domain, not the mechanism: "Feed", not "Feed (REST)"; "Manage your invoices", not "Generated resource — customise the schema".
  • Seed believable data — real names, dates, statuses, amounts. Three rows of Alpha/Beta/Gamma read as a demo; a dozen realistic records read as a product.

Read the full file on GitHub · 90 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 9d ago First seen · 90 lines · 82 tokens per session scan A 53da302f4236

Subscribe to this mod's changes

scaffold-dashboard is a skill published in the GitHub repository ahpxex/open-dashboard (139 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 1,078 once invoked, about $0.0004 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.

Analytics and metricsFrontendadmin-dashboardadmin-templateagent-skillsai-agentsback-officebetter-auth
Related

Other skills, from other repositories

kiranism-shadcn-dashboard

Guide for building features, pages, tables, forms, themes, and navigation in this Next.js 16 shadcn dashboard template. Use this skill whenever the user wants to add a new page, create a feature module, build a data table, add a form, configure navigation items, add a theme, set up RBAC access control, or work with…

Kiranism/next-shadcn-dashboard-starter · 142 tokens

tanstack-form

Headless, performant, and type-safe form state management for TS/JS, React, Vue, Angular, Solid, Lit, and Svelte.

Kiranism/next-shadcn-dashboard-starter · 34 tokens

tanstack-query

TanStack Query v5 data fetching patterns including useSuspenseQuery, useQuery, mutations, cache management, and API service integration. Use when fetching data, managing server state, or working with TanStack Query hooks.

Kiranism/next-shadcn-dashboard-starter · 48 tokens

next-best-practices

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling.

Kiranism/next-shadcn-dashboard-starter · 38 tokens

owl-admin-amis-page

A reference skill for building Owl Admin pages with amis, a system for defining admin interfaces such as forms, tables, filters, and actions through schemas.

slowlyo/owl-admin · 84 tokens

owl-admin-frontend-assets

A development guide for the browser-side files and published assets used by Owl Admin, a Laravel-based administration system. It covers admin views, themes, layouts, React work, and asset publishing.

slowlyo/owl-admin · 80 tokens