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.
/plugin marketplace add TarrySingh/hulde-review/plugin install hulde-reviewWrote 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/tarrysingh/hulde-review/hulde-dashboard)<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.
<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>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.00017 | $0.00487 |
| Opus 5 | $0.00009 | $0.00244 |
| Sonnet 5 | $0.00003 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00049 |
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.
What it actually says
/hulde-dashboard
Start the Hulde Review dashboard to visualize the knowledge graph for the current project.
Instructions
-
Determine the project directory:
- If
$ARGUMENTScontains a path, use that as the project directory - Otherwise, use the current working directory
- If
-
Check that
.hulde-review/knowledge-graph.jsonexists in the project directory. If not, tell the user:No knowledge graph found. Run /hulde-review first to analyze this project. -
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/
-
Install dependencies and build if needed:
cd <dashboard-dir> && pnpm install --frozen-lockfile 2>/dev/null || pnpm installThen ensure the core package is built (the dashboard depends on it):
cd <plugin-root> && pnpm --filter @hulde-review/core build -
Start the Vite dev server pointing at the project's knowledge graph:
cd <dashboard-dir> && GRAPH_DIR=<project-dir> npx vite --openRun this in the background so the user can continue working.
-
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_DIRenvironment variable tells the dashboard where to find the knowledge graph
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.
- 11d ago First seen · 58 lines · 17 tokens per session scan A e0f45053b02d
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.
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.
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.
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…
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…
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.
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.