What is agent-dashboard-cf?

A four-tab dashboard for viewing the health, activity, system state, AI setup, and usage of an agent environment running on Cloudflare Workers. A local collector sends data to the dashboard.

Use it to add or debug dashboard features, inspect services, network ports, vault data, scheduled jobs, models, skills, providers, and usage trends.

It gathers information from many local system and agent sources into one view, making problems and recent activity easier to inspect. The input does not describe every collector in detail.

agent-dashboard-cf — Skill for Claude Code and Codex by humanerd-drew

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 humanerd-drew/opencode-drewgent --skill agent-dashboard-cf

Clone the repo

git clone --depth 1 https://github.com/humanerd-drew/opencode-drewgent

Made for: Claude Code, Codex.

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/humanerd-drew/opencode-drewgent/agent-dashboard-cf/github.svg)](https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/agent-dashboard-cf)

Your own site

<a href="https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/agent-dashboard-cf"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/agent-dashboard-cf/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/humanerd-drew/opencode-drewgent/agent-dashboard-cf"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/agent-dashboard-cf.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 3,510 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 2 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.00000	$0.03510
Opus 5.5	$0.00000	$0.01404
Sonnet 5.5	$0.00000	$0.00702
Haiku 4.5	$0.00000	$0.00351

Measured 1mo ago against content hash 0d228014d85c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-dashboard-cf scanned grade A with 2 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 1mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

Python urllib default UA blocked → set Mozilla UA:

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

# Pass to subprocess.run(env={**_EXTRA_ENV, **os.environ})

skills/devops/agent-dashboard-cf/SKILL.md · 347 lines

How it starts

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

Agent Dashboard (Cloudflare Workers)

4-tab insight-driven dashboard. Load this skill when the user asks about the agent dashboard — adding features, fixing display issues, debugging pusher collectors, or expanding tab content.

Architecture

로컬 Mac (cron: 5min push)           Cloudflare Worker
─────────────────────────────        ──────────────────
pusher (agent_dashboard_push.py)     src/index.js
  ├─ 23 collectors                    ├─ POST /api/push → KV(latest)
  ├─ system/launchd/kanban/          ├─ GET  /api/status ← KV(latest)
  ├─ cron/network/vault/graph/       └─ GET  / (static assets)
  ├─ errors/usage/models/brain/
  ├─ today/timeline/live/misc/
  └─ session_details/provider/weekly → JSON → KV

Tab-Based Layout (Final)

HEALTH BANNER (green/yellow/red, issue count)
ACTIVITY ROW (Live dot + session IDs + elapsed + event count)

[Overview] [System] [Brain] [Usage]

Overview — 4 Hero cards (click→details) + Vault Graph (square, 1:1) + Kanban + Cron
System   — 4 Hero cards + Services(PID) + Network(Ports) + Vault(layers) + Misc
Brain    — 4 Hero cards + Models table + Skills categories + Providers + Gateway
Usage    — 4 Hero cards + 7-Day Trend chart + Hourly chart + Events + Sessions + Errors

Design Principles

Insight-first, not data-first. Every card answers "what should I know?"
Tab-based depth. >15 sections → tabs. Single page = summary only.
Live activity > static metrics. The live event stream from agent.log is the single biggest UX win.
15s full refresh. Gentle/DOM-preserving updates add complexity for marginal benefit.
Error grouping. Group by message prefix, show count. Never repeat the same error 8 times.

Key Implementation Patterns

HTML Structure

<div id="status" class="loading">Connecting...</div>
<div id="content">
  <div class="ar" id="activityRow"></div>
  <div class="tabs">...</div>
  <div class="page" id="p-overview">...</div>
  <div class="page" id="p-system">...</div>
  ...
</div>

Read the full file on GitHub · 347 lines

Files

What ships with it

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

1mo ago First seen · 347 lines · 0 tokens per session scan A 0d228014d85c

Subscribe to this mod's changes

agent-dashboard-cf is a skill published in the GitHub repository humanerd-drew/opencode-drewgent (3 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,510 tokens. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Analytics and metrics

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens

agent-dashboard-cf