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 vinnie357/claude-skills --skill webuigit clone --depth 1 https://github.com/vinnie357/claude-skillsWrote 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/vinnie357/claude-skills/webui)<a href="https://agentmods.dev/skills/vinnie357/claude-skills/webui"><img src="https://agentmods.dev/badge/skills/vinnie357/claude-skills/webui/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/vinnie357/claude-skills/webui"><img src="https://agentmods.dev/badge/skills/vinnie357/claude-skills/webui.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 49 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00030 | $0.00696 |
| Opus 5 | $0.00015 | $0.00348 |
| Sonnet 5 | $0.00006 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
webui 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dagu Web UI
Use this skill when working with Dagu's web interface to manage workflows, view execution history, monitor running workflows, or configure the UI.
Core Capabilities
The Dagu Web UI provides:
- Workflow Management - View, start, stop, and manage workflows
- Execution Monitoring - Real-time status and logs
- History Viewing - Past execution records and results
- DAG Visualization - Visual representation of workflow structure
- Log Access - View detailed execution logs
- Schedule Management - Configure when workflows run
Quick Start
Access Dagu Web UI at http://localhost:8080 (default) after starting Dagu:
dagu server
Primary Operations
Start a Workflow
To manually execute a workflow:
- Navigate to workflow list
- Click the workflow name
- Click "Start" button
- View real-time execution progress
Monitor Execution
For detailed information on a running workflow, consult references/monitoring.md which covers:
- Reading execution logs
- Understanding status indicators
- Tracking step progress
- Identifying failures
View History
Execution history is not unconditionally preserved — the REST API supports deleting individual records (DELETE /dags/{dagName}/history/{requestId}, see /dagu:rest-api references/api-endpoints.md "Delete Execution History"). Open a workflow's history to review past runs, find failed executions, and retry them (see Common Tasks).
Workflow Visualization
The DAG view shows workflow structure. Click step names in the DAG view for step-specific details.
When to Consult References
Read references/monitoring.md for execution status indicators, real-time log viewing, progress tracking, error detection, and troubleshooting stuck workflows.
Common Tasks
Restart a Failed Workflow
- Find the failed execution in history
- Click the retry/restart button
- Monitor the new execution
Stop a Running Workflow
- Navigate to the running workflow
- Click "Stop" or "Cancel"
- Confirm the action
- View cleanup handlers execution
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 · 99 lines · 30 tokens per session scan A 21ad9abb400c
webui is a skill published in the GitHub repository vinnie357/claude-skills (25 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 696 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-09-03.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…