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 agentmods add skills/dynos-fit/dynos-work/dashboardnpx skills add dynos-fit/dynos-work --skill dashboardgit clone --depth 1 https://github.com/dynos-fit/dynos-workWrote 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/dynos-fit/dynos-work/dashboard)<a href="https://agentmods.dev/skills/dynos-fit/dynos-work/dashboard"><img src="https://agentmods.dev/badge/skills/dynos-fit/dynos-work/dashboard.svg" alt="Measured on agentmods" 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.00039 | $0.00332 |
| Opus 5 | $0.00019 | $0.00166 |
| Sonnet 5 | $0.00008 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
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 6d 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.
What it actually says
dynos-work: Dashboard
Start the SPA dashboard server. Shows all registered projects in a unified web UI.
Ruthlessness Standard
- Do not invent server state, URLs, or process health.
- Report the exact command outcome. If startup fails, surface the failure plainly.
- If the server is already running or broken, say that directly instead of implying success.
Usage
/dynos-work:dashboard # start server at :8765
/dynos-work:dashboard stop # stop server
/dynos-work:dashboard restart # restart server
What you do
serve (default)
python3 "${REPO_DIR}/telemetry/dashboard.py" serve
Print the URL: http://127.0.0.1:8765
stop
python3 "${REPO_DIR}/telemetry/dashboard.py" kill
restart
python3 "${REPO_DIR}/telemetry/dashboard.py" restart
Notes
The dashboard runs as a background HTTP server. It survives after the conversation ends. Use stop to shut it down.
The dashboard shows:
- Global daemon status and aggregate stats
- Per-project cards (click to expand full detail)
- Active routes, recent tasks, benchmark runs, findings
- Autofix PRs per project
- Maintenance cycle history
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.
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.
- 6d ago First seen · 56 lines · 39 tokens per session scan A df896446f0a0
dashboard is a skill published in the GitHub repository dynos-fit/dynos-work (2 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 332 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.
Other skills, from other repositories
ring:generating-release-guides
Generating an internal Operations-facing update/migration guide from the git diff between two refs, documenting per-change client impact, deploy ordering, monitoring, and rollback notes in English, pt-br, or both. Use when preparing a version release or recording what changed for the Ops team. Runs read-only by…
profile
/profile - Session Profile Manager.
forge-quench
Systematically reduce .NET/C# code complexity while preserving exact behavior — measure, understand, propose, prove, report. Use after a feature is complete and tests pass, when code works but is harder to maintain than it should be.
onboarding
Walk a new developer through .NET project setup, architecture, key files, and first task. Use when someone new joins the team or needs to understand the codebase.
test-sweep
Run all test suites (unit, integration, API, E2E) and aggregate results into a summary report. Use after completing execution slices or before the Review Gate.
handoff
Create a self-contained temporary handoff document when the user asks to transfer the session to a new chat or runs /handoff.