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 agentmods add skills/daaaaave/agentic-workspace-core/frontend-ui-workflownpx skills add Daaaaave/agentic-workspace-core --skill frontend-ui-workflowgit clone --depth 1 https://github.com/Daaaaave/agentic-workspace-coreWrote 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/daaaaave/agentic-workspace-core/frontend-ui-workflow)<a href="https://agentmods.dev/skills/daaaaave/agentic-workspace-core/frontend-ui-workflow"><img src="https://agentmods.dev/badge/skills/daaaaave/agentic-workspace-core/frontend-ui-workflow.svg" alt="Measured on agentmods" 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 | $0.00085 | $0.03087 |
| Opus 5 | $0.00043 | $0.01543 |
| Sonnet 5 | $0.00017 | $0.00617 |
| Haiku 4.5 | $0.00009 | $0.00309 |
Grade A, and why
frontend-ui-workflow 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 5d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend UI Workflow
Goal
Ship UI that is product-grounded, tasteful for its audience, accessible, responsive, consistent with local components/tokens, and verified in the running app.
Principles
- UI quality includes design-system fit, hierarchy, states, responsive behavior, accessibility, and runtime evidence.
- Default to production-grade UI work. For non-trivial visual changes, run the full loop: local system, product fit, correct owner, states, responsive behavior, accessibility, and running-app evidence.
- Strong UI needs a clear product-fit point of view carried through composition, typography, spacing, color, surface/background, assets, and motion.
- Prefer the smallest coherent change that preserves the product's visual system.
- If a fix belongs in a shared component, token, layout primitive, or repeated pattern, update that owner or state the scope expansion before widening.
- Existing product decisions beat generic taste rules. Improve within them unless the task is a redesign or migration.
Use When
- Building or changing a page, screen, component, app shell, form, dashboard, landing page, onboarding flow, settings surface, empty state, navigation pattern, or marketing surface.
- Changing layout, spacing, typography, color, motion, hierarchy, interaction states, responsive behavior, accessibility, or visible UI behavior.
- Redesigning, polishing, improving taste, reducing generic AI output, or fixing "something looks off."
- Reviewing frontend code or rendered UI for design-system drift, visual regressions, responsive risk, state coverage, accessibility, or component architecture.
- Implementing from Figma, screenshots, URLs, brand references, product mockups, or an existing design system.
- Repairing frontend bugs where the cause or fix affects layout, state rendering, browser behavior, accessibility, or shared components.
Do Not Use When
- The task is backend-only, data-only, infrastructure-only, CLI-only, or documentation-only.
- The user asks only for external research; use
research-to-knowledge. - The user asks to create or change a skill; use
write-agent-skill. - The user asks only to inspect or update durable project knowledge; use
project-knowledge. - The user asks only for temporary transfer state; use
write-agent-handoff. - The edit is copy-only with no layout, state, accessibility, interaction, or visual-system risk.
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.
- 5d ago First seen · 219 lines · 85 tokens per session scan A c94c80b782b8
frontend-ui-workflow is a skill published in the GitHub repository Daaaaave/agentic-workspace-core (6 stars, last pushed 2mo ago), licensed MIT. It adds 85 tokens to every session and 3,087 once invoked, about $0.0004 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
epiphany
Roam the Ultan memory library and surface ONE non-obvious, useful connection between distant entries — an on-demand "epiphany". Use when the user asks for a spark/insight/epiphany from their memory, wants a hidden cross-cutting pattern surfaced, asks "show me something interesting in my notes", or runs /epiphany. Can…
ultan-search
Search and traverse the user's Ultan memory library (/.agent-mem/knowledge/). Use whenever you see an Ultan wikilink in priming context (e.g. [[projects/foo/bar]]) and want to read it, OR when you want to find entries by topic. Accepts a wikilink/path (returns the entry plus directory context — siblings, subfolders…
openlore
Query and publish to an OpenLore knowledge base over SSH using ordinary shell commands. Use when a task needs project documentation, runbooks, shared team knowledge, or a place to publish findings.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
github-code-review
Review PRs: diffs, inline comments via gh or REST.
simplify-code
Sequential 3-lens cleanup of recent code changes.