hecate ui.instructions.md

A set of rules for building Hecate’s operator interface, the screen used to monitor and control the system. It covers the project’s existing interface components, data formats, and checks for TypeScript code.

In plain words
What is it for?
Use it when changing the Hecate UI, API clients, shared interface components, or UI tests and type checks.
Why use it?
It helps keep the interface consistent with the rest of the application and prevents mismatches between the screen and the Go server’s responses.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/hecatehq/hecate/ui
Clone the repo
git clone --depth 1 https://github.com/hecatehq/hecate

Made for: GitHub Copilot.

Per session 145 This file is loaded in full into every session.
When invoked 145 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00145 $0.00145
Opus 5 $0.00072 $0.00072
Sonnet 5 $0.00029 $0.00029
Haiku 4.5 $0.00015 $0.00015

Measured 3d ago against content hash 63618cd28966, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

hecate ui.instructions.md 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 3d 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.

.github/instructions/ui.instructions.md · 20 lines

What it actually says

Operator UI

For UI work, read ui/AGENTS.md and docs-ai/skills/ui/SKILL.md before editing.

High-signal rules:

  • Build for an operator console: dense, calm, scannable workflows over marketing-style composition.
  • Reuse existing primitives, design tokens, API helpers, and test setup.
  • Keep TypeScript mirrors in sync with Go API response shapes.
  • Hecate-native endpoints use {object, data} envelopes; UI clients should read payload.data.
  • Verify with cd ui && bun run typecheck && bun run test; never use bun test.
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. 3d ago First seen · 20 lines · 145 tokens per session scan A 63618cd28966

Subscribe to this mod's changes

hecate ui.instructions.md is an instructions file published in the GitHub repository hecatehq/hecate (22 stars, last pushed 9d ago), licensed MIT. It adds 145 tokens to every session, about $0.0007 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-30.