hulde-dashboard

hulde-dashboard is a skill for Claude Code from TarrySingh/hulde-review. It costs 17 tokens per session (487 once invoked), scanned A, original, MIT.

A command that opens a web dashboard for viewing a codebase’s knowledge graph, a map of relationships between its code and other project elements.

In plain words
What is it for?
Use it to inspect an existing project knowledge graph through an interactive browser dashboard.
Why use it?
It makes the results of a Hulde Review analysis easier to explore visually than reading the raw data file.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the hulde-review plugin — 7 skills, 2 agents shipped together

Good fit Use it to inspect an existing project knowledge graph through an interactive browser dashboard.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add TarrySingh/hulde-review
Claude Code
/plugin install hulde-review

Made for: Claude Code.

Or install hulde-review, the plugin that ships this one along with the rest of its 7 skills, 2 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 hulde-dashboard

README.md
[![agentmods](https://agentmods.dev/badge/skills/tarrysingh/hulde-review/hulde-dashboard/github.svg)](https://agentmods.dev/skills/tarrysingh/hulde-review/hulde-dashboard)
Your own site
<a href="https://agentmods.dev/skills/tarrysingh/hulde-review/hulde-dashboard"><img src="https://agentmods.dev/badge/skills/tarrysingh/hulde-review/hulde-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.

agentmods 80×15 button for hulde-dashboard

Your own site · 80×15
<a href="https://agentmods.dev/skills/tarrysingh/hulde-review/hulde-dashboard"><img src="https://agentmods.dev/badge/skills/tarrysingh/hulde-review/hulde-dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 487 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.00017 $0.00487
Opus 5 $0.00009 $0.00244
Sonnet 5 $0.00003 $0.00097
Haiku 4.5 $0.00002 $0.00049

Measured 11d ago against content hash e0f45053b02d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

hulde-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 11d 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.

hulde-review-plugin/skills/hulde-dashboard/SKILL.md · 58 lines

What it actually says

/hulde-dashboard

Start the Hulde Review dashboard to visualize the knowledge graph for the current project.

Instructions

  1. Determine the project directory:

    • If $ARGUMENTS contains a path, use that as the project directory
    • Otherwise, use the current working directory
  2. Check that .hulde-review/knowledge-graph.json exists in the project directory. If not, tell the user:

    No knowledge graph found. Run /hulde-review first to analyze this project.
    
  3. Find the dashboard code. The dashboard is at packages/dashboard/ relative to this plugin's root directory. Use the Bash tool to resolve the path:

    PLUGIN_ROOT="$(cd "$(dirname "$0")/../.." && pwd)"
    

    Or locate it by checking these paths in order:

    • ${CLAUDE_PLUGIN_ROOT}/packages/dashboard/
    • The parent directory of this skill file, then ../../packages/dashboard/
  4. Install dependencies and build if needed:

    cd <dashboard-dir> && pnpm install --frozen-lockfile 2>/dev/null || pnpm install
    

    Then ensure the core package is built (the dashboard depends on it):

    cd <plugin-root> && pnpm --filter @hulde-review/core build
    
  5. Start the Vite dev server pointing at the project's knowledge graph:

    cd <dashboard-dir> && GRAPH_DIR=<project-dir> npx vite --open
    

    Run this in the background so the user can continue working.

  6. Report to the user:

    Dashboard started at http://localhost:5173
    Viewing: <project-dir>/.hulde-review/knowledge-graph.json
    
    The dashboard is running in the background. Press Ctrl+C in the terminal to stop it.
    

Notes

  • The dashboard auto-opens in the default browser via --open
  • If port 5173 is already in use, Vite will pick the next available port
  • The GRAPH_DIR environment variable tells the dashboard where to find the knowledge graph
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. 11d ago First seen · 58 lines · 17 tokens per session scan A e0f45053b02d

Subscribe to this mod's changes

hulde-dashboard is a skill published in the GitHub repository TarrySingh/hulde-review (2 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 487 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

architecture-decision-record

ADR templates in the Nygard format with context, decision, consequences, and alternatives. Use when writing ADRs, recording an architectural decision, or evaluating options.

yonatangross/orchestkit · 38 tokens

scope-appropriate-architecture

Right-sizes architecture to project scope, classifying projects into 6 tiers to prevent over-engineering. Use when designing architecture, selecting patterns, or detecting a project tier.

yonatangross/orchestkit · 41 tokens

dist-extras

This skill should be used when the user asks to "publish to PyPI", "generate an install script", "curl install", "publish to Claude Code marketplace", "create marketplace.json", "PyPI trusted publishing", "private plugin", "plugin drift", "pin refresh", or needs help with non-Homebrew distribution channels (PyPI…

Data-Wise/craft · 112 tokens

plan-orchestrator

This skill should be used when the user asks to "generate an ORCHESTRATE file", "turn a spec into a plan", "scaffold a feature breakdown", "scaffold a sprint backlog", "plan a sprint" (when a committed backlog/artifact is wanted, not just strategy advice), "generate roadmap artifacts", "create an implementation plan…

Data-Wise/craft · 138 tokens

release

This skill should be used when the user asks to "release", "create a release", "ship it", "publish a new version", "bump version and release", "cut a release", or mentions releasing to GitHub/npm/PyPI. Orchestrates the full release pipeline from pre-flight checks through GitHub release creation.

Data-Wise/craft · 70 tokens

project-detector

This skill should be used when the user asks to "detect project type", "what kind of project is this", "generate CI workflow", "set up CI", or needs to identify build tools, test frameworks, and CI requirements. Smart detection of project types, build tools, and CI requirements for automated workflow generation.

Data-Wise/craft · 68 tokens