A project dashboard that reads a PlanKit progress file to show feature, mission, and version-release progress. It works only in projects set up with a PlanKit folder.

Use it to answer status questions, review completed work, and check progress toward shipping a version.

It gives you one place to check what is done and where the current version stands, without manually piecing together updates from planning files.

dashboard — Skill for Claude Code and Codex by FlineDev: A project dashboard that reads a PlanKit progress file…

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 skills/flinedev/plankit/dashboard

Any agent

npx skills add FlineDev/PlanKit --skill dashboard

Clone the repo

git clone --depth 1 https://github.com/FlineDev/PlanKit

Made for: Claude Code, Codex.

Or install plankit, the plugin that ships this one along with the rest of its 5 skills, 4 commands.

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

When invoked 1,351 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.

Model	Per session	Once invoked
Fable 5	$0.00101	$0.01351
Opus 5	$0.00051	$0.00675
Sonnet 5	$0.00020	$0.00270
Haiku 4.5	$0.00010	$0.00135

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

Security

Grade A, and why

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

skills/dashboard/SKILL.md · 122 lines

How it starts

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

Dashboard

Automatic project dashboard — tracks feature progress, mission completion, and version releases via Progress.md.

This skill has no command. It triggers automatically when the user discusses status, completion, or releases. Other PlanKit skills (roadmap-planning, mission-breakdown) also update Progress.md directly as part of their workflows.

Config Preamble

Before any operation, locate the PlanKit folder and read its config:

Check if PlanKit/ exists in the project root. If not, check plan-kit/.
If neither exists, tell the user: "No PlanKit folder found. Run /plankit:init to set up PlanKit first."
Read .config.json from the PlanKit folder to get the naming convention.

Determine file paths:

Progress: PlanKit/Progress.md or plan-kit/progress.md
Features dir: PlanKit/Features/ or plan-kit/features/
Roadmap: PlanKit/Roadmap.md or split PlanKit/Roadmap/
- Or: plan-kit/roadmap.md or split plan-kit/roadmap/

View Dashboard

When the user asks about status/progress:

Read Progress.md — if it doesn't exist, tell the user: "No Progress.md yet. It's created when you plan your first version with /plankit:roadmap-planning."

Display a visual summary in chat:

═══════════════════════════════════════════════════
📊 DASHBOARD — vX.Y — Version Subtitle
═══════════════════════════════════════════════════

Feature Name                          [▓▓▓▓░░░░] 2/4
  ✅ Mission One
  ▶  Mission Two (current)
  ○  Mission Three
  ○  Mission Four

Another Feature                       Planned
  (No missions yet)

Third Feature                         [▓▓▓▓▓▓▓▓] Done
  ✅ Only Mission

───────────────────────────────────────────────────
Overall: 3/5 missions done · 1 in progress · 1 planned
═══════════════════════════════════════════════════

Offer actions if there's something actionable:
- If a mission is marked [>], mention it's the current focus
- If all missions for a feature are [x], suggest marking the feature as Done
- If all features are Done, suggest releasing the version

Read the full file on GitHub · 122 lines

Files

What ships with it

1 file 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.

references/DASHBOARD_FORMAT.md 3.2 KB

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.

3d ago First seen · 122 lines · 101 tokens per session scan A 0b6c94d66658

Subscribe to this mod's changes

dashboard is a skill published in the GitHub repository FlineDev/PlanKit (20 stars, last pushed 4mo ago), licensed MIT. It adds 101 tokens to every session and 1,351 once invoked, about $0.0005 per session on Opus 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-30.

Project management

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 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