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 sergekostenchuk/ui-ux-agent-skill-system --skill workflow-compliance-supervisorgit clone --depth 1 https://github.com/sergekostenchuk/ui-ux-agent-skill-systemWrote 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/sergekostenchuk/ui-ux-agent-skill-system/workflow-compliance-supervisor)<a href="https://agentmods.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/workflow-compliance-supervisor"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/workflow-compliance-supervisor/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/sergekostenchuk/ui-ux-agent-skill-system/workflow-compliance-supervisor"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/workflow-compliance-supervisor.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.00098 | $0.00917 |
| Opus 5 | $0.00049 | $0.00458 |
| Sonnet 5 | $0.00020 | $0.00183 |
| Haiku 4.5 | $0.00010 | $0.00092 |
Grade A, and why
workflow-compliance-supervisor 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 7d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Compliance Supervisor
This skill is the governance layer for journey-driven UI/UX projects. It checks whether the system did what it promised, whether skipped stages are justified, and whether the user sees honest reasons and next actions.
It does not execute design/build tasks and does not override senior-ui-ux-orchestrator.
Operating Modes
gate: check the current project before continuing or closing a phase.review: audit an existing task plan, progress state, progress screen, and evidence set.log: append or validateworkflow-log.jsonlevents.fixture-test: run lazy-skip and fake-evidence fixtures.explain: explain to the user why a stage is paused, skipped, returned to rework, or blocked.
Required Workflow
- Read references/decision-framework.md.
- Read references/evidence-and-log-rules.md.
- Read references/user-messaging.md if the output will be shown to a non-technical user.
- Locate the canonical project
TASK-PLAN.md. - Locate the declared journey registry. Default local registry:
$UIUX_SKILL_SYSTEM_ROOT/data/journey-registry.json. - Compare declared journey stages with task-plan claims, progress state, reports, screenshots, and logs.
- Produce one decision per affected stage:
continue,pause_for_user,return_to_rework,skip_with_reason, orblock. - For every skip, require an acceptable reason code, impact, and next action.
- For every
done/Ranclaim, require real evidence. - Write or update a sanitized report/log only when the user asked for execution or validation.
Decision States
continue: evidence is sufficient or deviation has no material impact.pause_for_user: missing user data, approval, budget, credentials, or production confirmation.return_to_rework: claimed completion lacks evidence or violates the journey contract.skip_with_reason: stage is intentionally skipped with accepted reason and visible impact.block: continuing would compromise quality, privacy, legality, production safety, or journey integrity.
What ships with it
6 files 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.
- 7d ago First seen · 80 lines · 98 tokens per session scan A e61c9278c57f
workflow-compliance-supervisor is a skill published in the GitHub repository sergekostenchuk/ui-ux-agent-skill-system (23 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 98 tokens to every session and 917 once invoked, about $0.0005 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.