dashboard

dashboard is a skill for Claude Code from laboramus-ai/laboramus-ai-claude-plugin. It costs 39 tokens per session (484 once invoked), scanned A, original, MIT.

A skill that builds a dashboard for tracking job applications. The dashboard shows application status, progress, fit scores, contact details, profile status, and available company information.

In plain words
What is it for?
Use it to create or refresh an application-tracking dashboard from the workspace's profile, application, company, status, and notes files.
Why use it?
It replaces scattered application files with one overview, making it easier to see what needs attention and how each application is progressing.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the laboramus-ai plugin — 11 skills, 2 agents shipped together

Good fit Use it to create or refresh an application-tracking dashboard from the workspace's profile, application, company, status, and notes files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/laboramus-ai/laboramus-ai-claude-plugin/dashboard
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 laboramus-ai/laboramus-ai-claude-plugin --skill dashboard
Clone the repo
git clone --depth 1 https://github.com/laboramus-ai/laboramus-ai-claude-plugin

Made for: Claude Code.

Or install laboramus-ai, the plugin that ships this one along with the rest of its 11 skills, 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.

agentmods badge for dashboard

README.md
[![agentmods](https://agentmods.dev/badge/skills/laboramus-ai/laboramus-ai-claude-plugin/dashboard/github.svg)](https://agentmods.dev/skills/laboramus-ai/laboramus-ai-claude-plugin/dashboard)
Your own site
<a href="https://agentmods.dev/skills/laboramus-ai/laboramus-ai-claude-plugin/dashboard"><img src="https://agentmods.dev/badge/skills/laboramus-ai/laboramus-ai-claude-plugin/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.

agentmods 80×15 button for dashboard

Your own site · 80×15
<a href="https://agentmods.dev/skills/laboramus-ai/laboramus-ai-claude-plugin/dashboard"><img src="https://agentmods.dev/badge/skills/laboramus-ai/laboramus-ai-claude-plugin/dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 484 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.00484
Opus 5 $0.00019 $0.00242
Sonnet 5 $0.00008 $0.00097
Haiku 4.5 $0.00004 $0.00048

Measured 12d ago against content hash 5b5d1a2a15eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 12d 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 · 30 lines

What it actually says

Laboramus — Dashboard

Give the user one place to see everything. Primary form: a self-contained dashboard.html written into the Laboramus/ root — regenerated from the files on every run ("refresh the dashboard" = re-read the sources, rewrite the file). Present the file to the user after writing it.

Data sources (read the whole workspace)

status.json fields are defined in ../../references/status-schema.md — parse exactly those.

  • profile/candidate-profile.md → profile status (built? how many skills? last updated).
  • applications/*/status.json → display name, applicationStatus (preparing/applied/interview/offer/rejected/withdrawn), steps done, fitScore, dates.
  • applications/*/notes.md → latest contact date + next step.
  • companies/*/ → which companies have cached analyses.

What to render

A single page:

  • Profile card: status + last update.
  • Applications table: display name · company · applicationStatus (color-coded) · fit score · commute times (e.g. 🚆 35 Min. / 🚗 22 Min.) · progress row (employer ✓/—, role ✓/—, fit ✓/—, letter ✓/—, interview ✓/—) · latest contact + next step from notes.
  • Sort by updatedAt (newest first); show fit score and status prominently.
  • Per application, list the file names of its artifacts (analyses, strategy brief, cover letter, interview prep, notes) so the user knows what exists and where.

Self-contained HTML: inline CSS, no external scripts, no network calls — it must render offline from the file system.

Optional: Live Artifact

If the environment supports creating a persistent Artifact (Cowork sidebar), you MAY additionally offer one. Note honestly: an Artifact cannot read local workspace files by itself — refreshing means regenerating it. The dashboard.html on disk remains the source of truth.

Language

Labels and any descriptive text in the user's language.

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. 12d ago First seen · 30 lines · 39 tokens per session scan A 5b5d1a2a15eb

Subscribe to this mod's changes

dashboard is a skill published in the GitHub repository laboramus-ai/laboramus-ai-claude-plugin (2 stars, last pushed 13d ago), licensed MIT. It adds 39 tokens to every session and 484 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories