What is research-dashboard?

A dashboard that gathers research and work progress from Claude Code project session logs into one Markdown dashboard and a matching HTML view. It scans projects independently and combines their summaries.

Use it to scan projects, create progress summaries, maintain a shared dashboard, and view project status in Markdown or HTML.

It gives you one place to see progress that is otherwise spread across multiple project folders and session histories.

research-dashboard — Skill for Claude Code by jmleetpl

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add jmleetpl/claude-research-dashboard

Claude Code

/plugin install research-dashboard

Made for: Claude Code.

Or install research-dashboard, the plugin that ships this one along with the rest of its 1 skill, 2 agents.

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/jmleetpl/claude-research-dashboard/research-dashboard/github.svg)](https://agentmods.dev/skills/jmleetpl/claude-research-dashboard/research-dashboard)

Your own site

<a href="https://agentmods.dev/skills/jmleetpl/claude-research-dashboard/research-dashboard"><img src="https://agentmods.dev/badge/skills/jmleetpl/claude-research-dashboard/research-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/jmleetpl/claude-research-dashboard/research-dashboard"><img src="https://agentmods.dev/badge/skills/jmleetpl/claude-research-dashboard/research-dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,661 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.00330	$0.02661
Opus 5.5	$0.00132	$0.01064
Sonnet 5.5	$0.00066	$0.00532
Haiku 4.5	$0.00033	$0.00266

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

Security

Grade A, and why

research-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 2mo 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.

research-dashboard/skills/research-dashboard/SKILL.md · 154 lines

How it starts

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

Research Dashboard — Cross-Project Orchestrator

Scans and consolidates the progress of research/work scattered across many Claude Code projects into a single dashboard.

Execution mode: sub-agents (fan-out / fan-in). Scanners do not need to talk to each other (each analyzes one project independently); only their results are collected. So this uses parallel Agent tool calls without team overhead.

Paths

This plugin resolves paths at runtime — nothing is hardcoded.

Item	Path
Session log root	`~/.claude/projects/`
Dashboard root	`RESEARCH_DASHBOARD_DIR` (default `~/research-dashboard`)
Main dashboard	`<dashboard_root>/DASHBOARD.md`
Workspace	`<dashboard_root>/_workspace/`
Digests	`<dashboard_root>/_workspace/digests/{project_id}.json`
Status cards	`<dashboard_root>/_workspace/scans/{project_id}.json`
Plugin scripts	`${CLAUDE_PLUGIN_ROOT}/scripts/...`

The dashboard output directory is RESEARCH_DASHBOARD_DIR if set, otherwise ~/research-dashboard. The scripts create all needed directories automatically. Plugin-bundled scripts are referenced via the ${CLAUDE_PLUGIN_ROOT} environment variable that Claude Code exposes for the plugin root.

Phase 0: Context check (determine execution mode)

Check whether DASHBOARD.md exists in the dashboard root:
- Absent → initial full scan (Phases 1–3).
- Present + an "update/refresh/rescan" request → incremental update: compare last_active in _workspace/digests/_index.json against the actual mtime of each log directory, and run Phases 1–3 only for changed projects.
- Present + only a specific project mentioned → re-run that project only.
- Present + a simple query ("show status", "what's next") → answer by reading DASHBOARD.md without scanning. If the last refresh was more than 7 days ago, suggest a refresh.
If the user manually corrects a project's status in the dashboard → edit the dashboard and that status card directly (no scan needed).

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

2mo ago First seen · 154 lines · 0 tokens per session scan A 824cc71e26f0

Subscribe to this mod's changes

research-dashboard is a skill published in the GitHub repository jmleetpl/claude-research-dashboard (2 stars, last pushed 4mo ago), licensed MIT. It adds 330 tokens to every session and 2,661 once invoked, about $0.0013 per session on Opus 5.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.

Project management Research

research-dashboard next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
research-dashboardjmleetpl/claude-research-dashboard	Skill	2	4mo ago	MIT	A	330	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	today	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	99k	today	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code