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 skills/wolfenazz/yzpzcode/live-dashboardnpx skills add wolfenazz/YzPzCode --skill live-dashboardgit clone --depth 1 https://github.com/wolfenazz/YzPzCodeWrote 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/wolfenazz/yzpzcode/live-dashboard)<a href="https://agentmods.dev/skills/wolfenazz/yzpzcode/live-dashboard"><img src="https://agentmods.dev/badge/skills/wolfenazz/yzpzcode/live-dashboard.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 | $0.00097 | $0.02206 |
| Opus 5 | $0.00048 | $0.01103 |
| Sonnet 5 | $0.00019 | $0.00441 |
| Haiku 4.5 | $0.00010 | $0.00221 |
Grade A, and why
live-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 yesterday.
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
100% identical to live-dashboard — 2 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Live Dashboard
You are a senior product-designer-engineer building a Live Artifact — an HTML page that behaves like a working dashboard, not a mockup. Your output ships, not only renders.
Pre-flight (must complete before emitting any HTML)
Read assets/template.html— start from this skeleton verbatim. Do not rebuild the shell from scratch. Override only what the user's brief or the active DESIGN.md require.Read references/layouts.md— pick exactly one of the three documented layouts (A · classic dashboard,B · kanban-flavored,C · KPI-only hero). State your choice in your reply.Read references/components.md— copy KPI-card, sparkline, activity row, and database row markup verbatim, then re-skin per the active DESIGN.md. Do not invent new component shapes.Read references/connectors.md— only wheninputs.connector !== mock. Emit a siblingconnectors.jsonlisting every event the artifact subscribes to and every read endpoint it polls.Read references/checklist.md— every P0 row must be true before you emitindex.html. Quote each P0 row inline in your reply with[x]or[ ]. Do not emit while any P0 is unchecked.
Build order
- Lock visual direction from the active
DESIGN.md. Display face should be the system / sans face Notion-leaning systems use (SF Pro, Inter as body, never Inter Display as a hero face). Body 14/22. - Topbar: breadcrumb (
workspace_name / Workspace / page_title) on the left, a<live-pill>on the right showing one of three states:Live · synced(green pulse),Syncing…(blue),Stale · <ago>(amber, afterstale_after_seconds). - Page header: a Notion
page-emoji(a single, semantically relevant emoji — never a generic 🚀 ✨ 🔥), apage-titleat 40px weight 700 letter-spacing -0.01em, a meta row with last-edited-by + "Last refreshed " + the auto-toggle button + the Refresh button. - Callout explaining the Live Artifact contract — pulled-from-where, refresh-when. One line. No marketing language.
- KPI grid: respect
inputs.kpi_count. 1px hairline grid, no shadows, no rounded internal cards. Numbersfont-variant-numeric: tabular-nums, weight 600, letter-spacing -0.01em. Each KPI gets a small grey delta line (↑ 6 vs last week). - Two-column block: a sparkline card (SVG, hand-rolled, no chart library) + the activity feed card. Sparkline shows a 7-day series with subtle accent fill at 10% alpha and a 2px stroke.
- Linked database: a Notion-style table —
db-head(uppercase 12px label-grey) +db-rowrows. Status pills use the Notion five-color set (Done / In progress / Blocked / In review / To do). Person chips use a colored 18px round avatar with two-letter initials. - Footer: source attribution (
Source: Notion API · workspace <workspace_name>) and connector slug.
What ships with it
6 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.
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.
- yesterday First seen · 203 lines · 97 tokens per session scan A e5d1ff74581e
live-dashboard is a skill published in the GitHub repository wolfenazz/YzPzCode (13 stars, last pushed yesterday), licensed Apache-2.0. It adds 97 tokens to every session and 2,206 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to live-dashboard, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
golden-rss
Use when testing the rss golden build.
omh-rust
This is a Hermes-native rust workflow skill.
tui-migrate-setup
Migrates the supported subset of an existing Warp GUI setup into Warp Agent CLI without exposing credentials or application state. Use in Warp Agent CLI when a user wants to copy or move compatible settings or global file-based MCP servers from the desktop app, set up Warp Agent CLI from an existing GUI installation…
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
bib-coverage
Compare a project .bib against a Paperpile project/topic folder to find uncited papers or unfiled entries. Use when the user asks to compare a project .bib against a Paperpile project/topic folder to find uncited papers or unfiled entries.