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 skills add majiang213/OpenClaw-MAS --skill dashboard-buildergit clone --depth 1 https://github.com/majiang213/OpenClaw-MASWrote 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/majiang213/openclaw-mas/dashboard-builder)<a href="https://agentmods.dev/skills/majiang213/openclaw-mas/dashboard-builder"><img src="https://agentmods.dev/badge/skills/majiang213/openclaw-mas/dashboard-builder/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.
<a href="https://agentmods.dev/skills/majiang213/openclaw-mas/dashboard-builder"><img src="https://agentmods.dev/badge/skills/majiang213/openclaw-mas/dashboard-builder.svg" alt="Reviewed on agentmods" width="80" 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.00532 |
| Opus 5 | $0.00018 | $0.00266 |
| Sonnet 5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
dashboard-builder 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.
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.
This is a copy
88% identical to dashboard-builder — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dashboard Builder
Use this when the task is to build a dashboard people can operate from.
The goal is not "show every metric." The goal is to answer:
- is it healthy?
- where is the bottleneck?
- what changed?
- what action should someone take?
When to Use
- "Build a Kafka monitoring dashboard"
- "Create a Grafana dashboard for Elasticsearch"
- "Make a SigNoz dashboard for this service"
- "Turn this metrics list into a real operational dashboard"
Guardrails
- do not start from visual layout; start from operator questions
- do not include every available metric just because it exists
- do not mix health, throughput, and resource panels without structure
- do not ship panels without titles, units, and sane thresholds
Workflow
1. Define the operating questions
Organize around:
- health / availability
- latency / performance
- throughput / volume
- saturation / resources
- service-specific risk
2. Study the target platform schema
Inspect existing dashboards first:
- JSON structure
- query language
- variables
- threshold styling
- section layout
3. Build the minimum useful board
Recommended structure:
- overview
- performance
- resources
- service-specific section
4. Cut vanity panels
Every panel should answer a real question. If it does not, remove it.
Example Panel Sets
Elasticsearch
- cluster health
- shard allocation
- search latency
- indexing rate
- JVM heap / GC
Kafka
- broker count
- under-replicated partitions
- messages in / out
- consumer lag
- disk and network pressure
API gateway / ingress
- request rate
- p50 / p95 / p99 latency
- error rate
- upstream health
- active connections
Quality Checklist
- valid dashboard JSON
- clear section grouping
- titles and units are present
- thresholds/status colors are meaningful
- variables exist for common filters
- default time range and refresh are sensible
- no vanity panels with no operator value
Related Skills
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.
- 9d ago First seen · 110 lines · 37 tokens per session scan A d5e41e802489
dashboard-builder is a skill published in the GitHub repository majiang213/OpenClaw-MAS (5 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 532 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to dashboard-builder, differing in 27 lines, and is treated as a copy.
Other skills, from other repositories
sequence-diagram
Show interactions and flows over time. Illustrate request paths, asynchronous patterns, error handling. Use when documenting complex flows or onboarding on system behavior.
architecture-patterns-catalog
Reference catalog of proven architecture patterns. Know when to apply each pattern, tradeoffs, and examples. Use as reference when designing systems.
architecture-anti-patterns
Identify and avoid common architectural mistakes. Recognize patterns of failure. Use when reviewing designs or learning from mistakes.
architecture-review-facilitation
Lead effective architecture reviews. Manage discussions, surface disagreements, build consensus, document decisions. Use when conducting reviews or running architecture forums.
interview-prep
Prepare for architecture interview questions and scenarios. Practice system design, tradeoff discussions, communication. Use for career development and interview readiness.
system-audit
Conduct comprehensive system architecture evaluation. Assess design quality, technical debt, operational readiness, scalability. Use when auditing existing systems.