dashboards

A dashboard-building command generates HTML staging dashboards from project files, with each dashboard focused on a different kind of information.

In plain words
What is it for?
It is for rebuilding all dashboards or one named dashboard, including a searchable catalogue of available commands and a weekly report view.
Why use it?
It gives the team on-demand visual pages for inspecting commands, reports, and other project state.

Command

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.

agentmods
npx agentmods add commands/saigonxiii/evc/dashboards
Clone the repo
git clone --depth 1 https://github.com/SaigonXIII/evc
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,108 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.01108
Opus 5 $0.00000 $0.00554
Sonnet 5 $0.00000 $0.00222
Haiku 4.5 $0.00000 $0.00111

Measured 3d ago against content hash a48b77049cb1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dashboards 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 3d 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.

_templates/commands/dashboards.md · 125 lines

How it starts

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

/dashboards — Master Staging Dashboards Builder

The /dashboards command builds all master staging dashboards for EVC in one shot. Each dashboard serves one focused purpose and is rebuilt from source files on demand.

Usage

  • /dashboards — rebuild all master dashboards
  • /dashboards [name] — rebuild a specific dashboard (e.g. /dashboards canon-viewer)

Master Dashboards

All dashboards are written to staging/dashboards/.

1. master-commands.html

Visual reference of every command, hook, and context mode available in the EVC environment.

  • Group by category: Content Engine, Blog Engine, QA, Comms, Productivity, Onboarding, Chains
  • Use the .staging-grid + .staging-card pattern from staging-base.css
  • Each command card shows: name, short description, trigger, category pill
  • Include a search box with inline JS that filters cards by name or description on keyup
  • Read the command list by globbing .claude/commands/*.md files — parse the first heading or first paragraph as the description

2. weekly-report.html

The latest weekly report dashboard.

  • Read from content-engine/output/reports/w[latest].md, or generate from performance-review + intel-scan data if the report file is missing
  • Layout: stats row at top, then sections for:
    • X Performance (impressions, engagement, top posts)
    • Content Production (posts shipped, QA pass rate)
    • Linear / Tasks (closed, open, blockers)
    • Wins & Flags (bulleted highlights and risks)
  • Use .stats-row, .stat-card, .section classes from staging-base.css

3. canon-viewer.html

Visual viewer for brand/canon-rules.json — makes the JSON readable.

  • Banned phrases rendered as red chips/pills
  • Required language rendered as green chips/pills
  • USPs rendered as blue cards (one per USP, with title and description)
  • Compliance rules per jurisdiction shown as tabs or collapsible sections
  • Live vs defunct partners clearly separated (green check vs gray strikethrough)

4. brand-canvas.html

Read the full file on GitHub · 125 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.

  1. 3d ago First seen · 125 lines · 0 tokens per session scan A a48b77049cb1

Subscribe to this mod's changes

dashboards is a command published in the GitHub repository SaigonXIII/evc (56 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,108 tokens. 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.