Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sykoramade/helm-skillnpx agentmods add skills/sykoramade/helm-skill/helm-dashboardWrote 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/sykoramade/helm-skill/helm-dashboard)<a href="https://agentmods.dev/skills/sykoramade/helm-skill/helm-dashboard"><img src="https://agentmods.dev/badge/skills/sykoramade/helm-skill/helm-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.00077 | $0.01099 |
| Opus 5 | $0.00039 | $0.00549 |
| Sonnet 5 | $0.00015 | $0.00220 |
| Haiku 4.5 | $0.00008 | $0.00110 |
Grade A, and why
helm-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 8d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HELM Dashboard
What this is: one command that turns .helm/*.jsonl into a page the MD can
look at.
The standard it holds: every number on the page is derived from the log. Nothing is entered by hand, nothing is estimated silently, and anything estimated says so on the page.
Why it is a file and not a server
HELM's promise is "it's just markdown. No service, no account, no telemetry." A dashboard is the first feature that would break that promise, so this one does not: it writes a static HTML file with no external requests, no fonts, no scripts, and no daemon. You can open it, email it, commit it, or delete it. Delete is always safe — it is a render, never a source of truth.
If you ever feel the pull to add a live server, a websocket, or a hosted view, that is a different product and it needs the MD's explicit decision, not a convenient default.
Running it
python3 tools/helm_dashboard.py # this project -> .helm/dashboard.html
python3 tools/helm_dashboard.py --root <path> # a named project
python3 tools/helm_dashboard.py --root <root> --portfolio # every child project
python3 tools/helm_dashboard.py --out <path.html> # choose the output
python3 tools/helm_dashboard.py --stale-days 7 # tighten the staleness window
Dependency-free, stdlib only, Python 3.7+. It reads:
.helm/decisions.jsonl— status, phase, timeline, cost.helm/lessons.jsonl— the lessons panel.helm/verdict-cache.jsonl— cache entries.helm/founding-bet.md— the bet line shown under the project name
Missing files are simply absent from the page. It never fails because a ledger has not been created yet.
What it shows
- Status badge, derived by exactly the rules in
helm-portfolio:NEEDS-MD → BLOCKED → STALE → ON-TRACK(plusNO-DATAfor an empty log). The page and the Portfolio CEO's briefing can never disagree, because they read the same table. - Cost — total tokens, gates measured, cache replays, and an estimated saving.
- Lessons — the most recent entries, pattern first.
- Recent decisions — the last 25 log lines.
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.
- 8d ago First seen · 90 lines · 77 tokens per session scan A cf0e89bfe457
helm-dashboard is a skill published in the GitHub repository sykoramade/helm-skill (6 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 1,099 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…