dashboard

dashboard is a skill for Claude Code from reggiechan74/JobOps. It costs 30 tokens per session (2,786 once invoked), scanned A, original, MIT.

A job-application dashboard that reads a YAML tracker, a structured text file, and displays the current application pipeline with suggested next actions.

In plain words
What is it for?
Use it to review applications, reconcile tracker data, inspect the latest status, or render a board without changing the tracker.
Why use it?
It gives a quick view of application statuses and can reconcile the tracker with files on disk, reducing manual checking. On Codex, the board is read-only.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: names the AskUserQuestion tool; mentions Claude Code; mentions Codex.

Part of the jobops plugin — 26 skills, 17 agents shipped together

Good fit Use it to review applications, reconcile tracker data, inspect the latest status…

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

Made for: Claude Code.

Or install jobops, the plugin that ships this one along with the rest of its 26 skills, 17 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/reggiechan74/jobops/dashboard.svg)](https://agentmods.dev/skills/reggiechan74/jobops/dashboard)
Your own site
<a href="https://agentmods.dev/skills/reggiechan74/jobops/dashboard"><img src="https://agentmods.dev/badge/skills/reggiechan74/jobops/dashboard.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,786 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.00030 $0.02786
Opus 5 $0.00015 $0.01393
Sonnet 5 $0.00006 $0.00557
Haiku 4.5 $0.00003 $0.00279

Measured 7d ago against content hash b7e8267fe05e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 7d 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.

plugins/jobops/skills/dashboard/SKILL.md · 185 lines

How it starts

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

JobOps Application Dashboard

Reconciles tracker.yaml from the filesystem, renders a statusboard, and — on Claude Code — drives a two-level menu loop (pick an application, then pick an action). On Codex it renders a read-only board with suggested next actions.

Flags:

  • --board-only — reconcile and render the board, then stop (no menu loop) on any platform.
  • --fast — skip the reconcile entirely: render the board from the tracker exactly as stored, then stop (no scan, no tracker write, no menu loop). Use for a quick read-only glance; artifact flags and next_action reflect the last full reconcile, not the current filesystem. Takes precedence over --board-only (both stop after the board). If --fast and --board-only are passed together, --fast wins.

Configuration

Read .jobops/config.json. If missing, stop with:

JOBOPS NOT CONFIGURED Run /jobops:setup to initialize your workspace.

Use config.directories.<key> for all file paths in this skill.

Tracker path resolution (self-heal): read config.directories.application_tracker. If that key is absent, set it to {config.directories.applications_root}/tracker.yaml, load the full existing config object, add only directories.application_tracker (leaving every other key — directories.*, preferences, candidate, templates, migration — untouched), and write the whole object back atomically to .jobops/config.json.tmp in the same directory, then mv over .jobops/config.json, and use that path. This lets workspaces created before the dashboard existed work with no migration step.

Under --fast, resolve the path read-only: if the key is absent, use the default {config.directories.applications_root}/tracker.yaml without writing config back (a fast glance never mutates state). If no tracker file exists at the resolved path, print No tracker yet — run /jobops:dashboard (without --fast) to build it. and exit.


Reconcile

Run this every invocation, before rendering — unless --fast was passed, in which case skip this entire section and render the board directly from the stored tracker (no scan, no recompute, no write).

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

  1. 7d ago First seen · 185 lines · 30 tokens per session scan A b7e8267fe05e

Subscribe to this mod's changes

dashboard is a skill published in the GitHub repository reggiechan74/JobOps (25 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 2,786 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-30.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens