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 manishiitg/coding-agent-loop --skill work-dashboardgit clone --depth 1 https://github.com/manishiitg/coding-agent-loopWrote 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/manishiitg/coding-agent-loop/work-dashboard)<a href="https://agentmods.dev/skills/manishiitg/coding-agent-loop/work-dashboard"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/work-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/manishiitg/coding-agent-loop/work-dashboard"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/work-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.00036 | $0.01814 |
| Opus 5.5 | $0.00014 | $0.00726 |
| Sonnet 5.5 | $0.00007 | $0.00363 |
| Haiku 4.5 | $0.00004 | $0.00181 |
Grade A, and why
work-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 20d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crew Dashboard
Use this skill when the user asks for a dashboard, board, tracker, visual home, or another project view intended to organize or manage information visually.
Contract
- Dashboard documents are HTML files under
db/reports/;index.htmlis the backward-compatible default. Supporting assets belong underdb/assets/. - For multiple top-toolbar views, create one HTML document per useful view.
The toolbar discovers them automatically. Optionally add
db/reports/views.jsonwith{"schema_version":1,"default":"overview","views":[{"id":"overview","title":"Overview","path":"db/reports/index.html","order":0}]}to control titles, order, and the default. Paths must remain underdb/reports/and end in.html. - This is a general project artifact, not an AgentWorks workflow Dashboard. Do not create a workflow, plan, phase, step, route, Pulse configuration, or managed workflow merely to provide a Dashboard. A project-owned managed database is optional and should be added only when the view needs durable structured data.
- Inspect the existing
db/reports/folder before changing it. Preserve useful content and the user's established organization and visual language. - Build responsive documents. Use separate toolbar views for genuinely distinct destinations and internal sections/tabs for closely related material.
- Support both app themes using
:root.darkor[data-theme="dark"]. - Choose any CSS/component approach that fits the Dashboard, including plain CSS,
Tailwind, Bootstrap, daisyUI, another framework, or a combination that works
in the browser. Version-pinned HTTPS CDN stylesheets and browser scripts are
supported. If using daisyUI,
<html data-report-ui="daisyui">asks the host to inject its pinned CSS; daisyUI alone does not include Tailwind utilities. These are compatibility facts, not a preferred stack. - Choose any suitable charting approach, including Chart.js, another browser library, SVG/canvas, or HTML/CSS. Match the complexity of the implementation to the visualization, make it responsive and theme-aware, and show a readable fallback when an external dependency fails.
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.
- 20d ago Changed · +25 lines 879be7218c7e
- 26d ago Changed · +39 lines 64215a988915
- 29d ago Changed 92b094968d74
- 1mo ago Changed · +4 lines scan B → A b746ba3d5856
- 1mo ago Changed · +20 lines scan A → B 4aaa35e0cef1
- 1mo ago First seen · 55 lines · 36 tokens per session scan A d574b2e85740
work-dashboard is a skill published in the GitHub repository manishiitg/coding-agent-loop (13 stars, last pushed 19d ago), licensed MIT. It adds 36 tokens to every session and 1,814 once invoked, about $0.0001 per session on Opus 5.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-15.
Other skills, from other repositories
kungfu-agent-onboarding
Use when a user asks to understand, start, inspect, extend, or safely operate installed Kungfu; verify the installed pack, select one intent route, personalize the explanation, and propose one smallest safe next action.
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
goga-task-by-specifying
Interactive task formulation from a raw request.
goga-cell-go
Golang rules for implementing CODEMANIFEST contracts.
kano-backlog
Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this whenever the user wants to triage…