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 hecatehq/hecate --skill uigit clone --depth 1 https://github.com/hecatehq/hecateWrote 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/hecatehq/hecate/ui)<a href="https://agentmods.dev/skills/hecatehq/hecate/ui"><img src="https://agentmods.dev/badge/skills/hecatehq/hecate/ui/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/hecatehq/hecate/ui"><img src="https://agentmods.dev/badge/skills/hecatehq/hecate/ui.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.14482 |
| Opus 5.5 | $0.00017 | $0.05793 |
| Sonnet 5.5 | $0.00009 | $0.02896 |
| Haiku 4.5 | $0.00004 | $0.01448 |
Grade A, and why
hecate-ui 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 15d 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 — 983 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hecate UI skill
Use this skill for any work inside ui/. Backend work uses ../backend/SKILL.md.
Canonical guidance lives here
../../core/project-context.md— toolchain pin (Bun, React 19, Vite, Vitest),bun run test≠bun testwarning.../../core/engineering-standards.md— type-name mirroring with the Go side, design-token discipline, anti-patterns.../../core/workflow.md— operating loop, planning triggers, commit etiquette (UI agent-doc updates usechore:).../../core/verification.md— UI verification ladder, snapshot review, done criteria.
Product lens
The Hecate UI should feel like:
- An operator console.
- A runtime control surface.
- A debugging and inspection tool.
It should not feel like:
- A generic SaaS dashboard full of cards.
- A landing page with product-marketing copy.
- A toy chat surface without production context.
Default to utility, orientation, and workflow clarity.
Visual thesis
Calm, technical, and deliberate. Dense enough to be useful, sparse enough to scan. Strong hierarchy, minimal chrome, one clear accent system.
Prefer restrained layout, strong type hierarchy, clear sectioning without over-carding, obvious status and health states, meaningful spacing over decorative surfaces.
Avoid card mosaics, oversized hero copy, decorative gradients behind routine product UI, multiple accent colors fighting for attention, visual noise that hides runtime state.
Consistency guardrails
Before adding or changing UI, find the closest existing precedent and reuse it unless the product behavior truly differs. Hecate's UX should feel like one operator console, not a set of unrelated experiments.
- Reuse shared primitives for recurring patterns:
DropdownPicker,BrandAvatar,CopyableID,TranscriptActivityTimeline, badges, inline errors, and modal/slide-over chrome. - Keep button height, dropdown rhythm, icon treatment, metadata labels, empty-state spacing, and hover/focus affordances consistent across Chats, Tasks, Connections, Observability, and Usage.
- Long machine identifiers belong behind compact labels with tooltip + copy affordances. Prefer full context in Details or Task Detail over leaking raw ids into list rows.
- If a screen already has an empty, loading, repair, or onboarding precedent, extend that component/copy path instead of adding a second parallel state.
- When making Hecate Chat and External Agent behavior more similar, preserve their real runtime differences: Hecate owns task-backed tools; external agents own ACP-native sessions.
- Add role/name-based tests for shared controls and view-level tests for every state that previously regressed. E2E should cover cross-view navigation, onboarding, and setup/repair flows when a bug came from app composition.
- Before filing a PR or pushing a PR update that touches UI/TypeScript, run the
UI verification ladder:
cd ui && bun run typecheck,bun run lint,bun run format:check, andbun run test. Add same-change tests for production UI code, and targeted Playwright coverage when the change is a workflow, routing, onboarding, or regression fix. If Go files changed too, run the backend ladder as well.
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.
- 15d ago Changed · +11 lines 2d0132be2a1f
- 21d ago Changed · +11 lines c24cbdfeee0f
- 21d ago Changed · +16 lines 5f9f2a275411
- 26d ago Changed · +18 lines db4d5deadc6f
- 1mo ago First seen · 927 lines · 43 tokens per session scan A 95b8207a9706
hecate-ui is a skill published in the GitHub repository hecatehq/hecate (23 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 14,482 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
inspector-workbench
Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't…
trulens-instrumentation
Instrument LLM apps with TruLens OTEL-based tracing - from setup to debugging and optimization.
decocms-ui
Build or style React UI with the decocms product design system (@decocms/ui). Use when creating interfaces, pages, or components in a project that should look like decocms products, when the user mentions "design system", "@decocms/ui", "decocms style", or asks to make UI consistent with Studio. Covers installation…
rust-tracing
Add or change Rust diagnostic tracing in litellm-rust, including route spans, subscriber layers, and Python logger delivery.
list-npm-package-content
List the contents of an npm package tarball before publishing. Use when the user wants to see what files are included in an npm bundle, verify package contents, or debug npm publish issues.
mcp-apps-builder
MANDATORY for ALL MCP server work - mcp-use framework best practices and patterns. READ THIS FIRST before any MCP server work, including: Creating new MCP servers Modifying existing MCP servers (adding/updating tools, resources, prompts, widgets) Debugging MCP server issues or errors Reviewing MCP server code for…