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.
npx skills add sjarmak/coding-agent-workflows --skill dashboardgit clone --depth 1 https://github.com/sjarmak/coding-agent-workflowsWrote 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.
[](https://agentmods.dev/skills/sjarmak/coding-agent-workflows/dashboard)<a href="https://agentmods.dev/skills/sjarmak/coding-agent-workflows/dashboard"><img src="https://agentmods.dev/badge/skills/sjarmak/coding-agent-workflows/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.
<a href="https://agentmods.dev/skills/sjarmak/coding-agent-workflows/dashboard"><img src="https://agentmods.dev/badge/skills/sjarmak/coding-agent-workflows/dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00086 | $0.03215 |
| Opus 5 | $0.00043 | $0.01607 |
| Sonnet 5 | $0.00017 | $0.00643 |
| Haiku 4.5 | $0.00009 | $0.00321 |
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dashboard
Answer a status question about a repo with a page instead of a wall of terminal output. The model decides what matters and writes the answer; a shipped renderer turns that into HTML. The page is a snapshot, generated on demand, stamped with its own generation time and honest about the age of every panel.
When to use
- "dashboard" / "show me project status" / "what's going on in this repo"
- "what's blocking the release", "what needs me", "where did I leave off"
- A rollup across several checkouts: "dashboard across these repos"
- An explorable overview of what a project contains: "show me the skills and resources here", "map what's in this repo", "what can this project do"
- Not for: answering one narrow factual question (just run the command), or anything that needs live-updating state (this writes a static file).
ZFC boundary
Mechanism gathers and renders; the model decides and writes. Do not encode what counts as important into the renderer, and do not hand-write HTML.
- Mechanism: running read-only commands, the allowlist gate
(
allowlist.mjs), all markup, layout, escaping, staleness arithmetic, severity ordering (render.mjs), reading and writing the profile. - Model: which panels answer this question, which panel kind fits each collector's output, what the written answer says, what belongs in needs-attention and in what order of severity.
Invocation
Bare, the model picks a sensible default set for the repo. With a question, the panels are whatever answers that question and nothing else.
| Form | Behavior |
|---|---|
dashboard |
default panel set for this repo |
dashboard <question> |
whatever shape and contents answer the question |
dashboard --run <panel> |
same, but that panel's collector executes fresh |
dashboard rollup <path> <path> … |
one page, one collapsible section per repo |
Phase 0 — Workspace (mechanism)
Work in .dashboard/ at the repo root. On first use create it along with a
self-ignoring .gitignore containing a single * line, so the directory stays
untracked without ever editing the project's own .gitignore.
What ships with it
5 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.
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.
- 4d ago First seen · 306 lines · 86 tokens per session scan A 0d7070e81be4
dashboard is a skill published in the GitHub repository sjarmak/coding-agent-workflows (2 stars, last pushed 8d ago), licensed MIT. It adds 86 tokens to every session and 3,215 once invoked, about $0.0004 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-09-05.
Other skills, from other repositories
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
template-instantiation
Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
handover-admin
Generate comprehensive admin documentation for AEM Edge Delivery Services project handover. Use when handing over admin responsibilities, onboarding a new site administrator, or documenting admin procedures — e.g., "admin guide", "admin documentation", "admin handover".
to-issues
A planning aid that breaks a PRD or technical specification into small implementation issues, each covering a complete, demonstrable piece of work.
project-context-setup
Scaffolds per-repository agent context so coding agents share the same issue tracker rules, triage label vocabulary, domain glossary, ADR layout, and handoff conventions. Triggers on: "set up project context", "configure agent docs", "create CONTEXT.md", "setup agent workflow", "agent issue tracker setup", "triage…