What is aid-design-dashboard?

A planning aid for deciding what a dashboard should show, who will use it, where its data comes from, and how often it refreshes. It records these choices in a design file.

Use it to plan dashboard data sources, charts or other visualizations, intended users, and refresh schedules. It prepares a design for a separate build step.

It helps settle the dashboard’s purpose and contents before someone builds it, reducing unclear requirements and rework.

aid-design-dashboard — Skill for Claude Code by AndreVianna

Install

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.

Any agent

npx skills add AndreVianna/aid-methodology --skill aid-design-dashboard

Clone the repo

git clone --depth 1 https://github.com/AndreVianna/aid-methodology

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-design-dashboard/github.svg)](https://agentmods.dev/skills/andrevianna/aid-methodology/aid-design-dashboard)

Your own site

<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-design-dashboard"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-design-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-design-dashboard"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-design-dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 129 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 910 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00129	$0.00910
Opus 5	$0.00064	$0.00455
Sonnet 5	$0.00026	$0.00182
Haiku 4.5	$0.00013	$0.00091

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

Security

Grade A, and why

aid-design-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 11d 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.

.claude/skills/aid-design-dashboard/SKILL.md · 86 lines

How it starts

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

Design Dashboard (develop a design seed, resolve nothing)

Bind VERB=design, ARTIFACT=dashboard -- the design stage in the contract's vocabulary -- then follow the shared contract at .claude/aid/templates/design-lifecycle.md. This skill binds that contract and restates none of its rules. The seed it writes is .aid/design/dashboard.md; realizing it into the built dashboard is /aid-create-dashboard's job, not this one's.

Boundary vs /aid-create-dashboard: that skill builds the dashboard from a ready seed; this one only develops the seed. Neither resolves anything on its own -- the user decides when a seed is ready to realize.
Not a numbered pipeline phase; does not route to /aid-execute.

State machine: INTAKE -> DESIGN -> VERIFY (loop) -> PRESENT [user decides] -> DONE, as design-lifecycle.md § Skill shape defines it. Print the [State: NAME] -- {purpose} entry line on each state.

State: INTAKE

Require a subject. Empty argument -> ask one bootstrapping question ("What dashboard do you want to design -- its data source, visualizations, and refresh cadence?") and wait.
Allocate through the Work Initiation Gate exactly as the contract's Allocation rule requires (.claude/skills/aid-design/SKILL.md INTAKE step 4 is the shape), with initiator: aid-design-dashboard. phase is not driven.
Acquire .aid/design/ per the contract, then read .aid/design/dashboard.md if a prior seed exists -- re-invocation iterates it rather than starting over.
Classify complexity for the aid-architect dispatch (verifier tier >= producer).

Advance: DESIGN.

State: DESIGN

Dispatch aid-architect (clean context, tiered) to write or iterate .aid/design/dashboard.md in the seed shape the contract fixes (design-seed.md; feature-002 §4), grounded in .aid/knowledge/ and the project source plus any seed read in INTAKE. What this artifact's seed must settle: the data source, the visualizations, and the refresh cadence; its ## Destination names where the built dashboard lands. Never writes .aid/knowledge/ and never writes production code -- the design invariant (design-lifecycle.md).

Read the full file on GitHub · 86 lines

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.

11d ago First seen · 86 lines · 129 tokens per session scan A 810ace9fcf1e

Subscribe to this mod's changes

aid-design-dashboard is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed yesterday), licensed MIT. It adds 129 tokens to every session and 910 once invoked, about $0.0006 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.

Analytics and metrics Design and UX

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

aid-design-dashboard