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 agent-progress-visualizergit 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/agent-progress-visualizer)<a href="https://agentmods.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/agent-progress-visualizer"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/agent-progress-visualizer/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/agent-progress-visualizer"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/agent-progress-visualizer.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.00110 | $0.01593 |
| Opus 5 | $0.00055 | $0.00796 |
| Sonnet 5 | $0.00022 | $0.00319 |
| Haiku 4.5 | $0.00011 | $0.00159 |
Grade A, and why
agent-progress-visualizer 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 8d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Progress Visualizer
This skill creates and maintains a user-facing progress cockpit for UI/UX Agent Skill System projects. It translates canonical task-plan state into plain-language HTML for non-technical users.
It does not execute project tasks and does not own canonical status. Before planning, project-request.json and workflow-log.jsonl are only bootstrap sources. After planning, TASK-PLAN.md becomes the source of truth.
Operating Modes
bootstrap: create the first visible progress screen immediately after the system accepts a substantial user request, beforeTASK-PLAN.mdexists.init: create or replace the first task-plan-derived progress-state and progress screen afterTASK-PLAN.mdexists.update: regenerate state and HTML after task-plan, report, artifact, feedback, or wiki changes.review: inspect an existing progress screen for source-of-truth drift, fake status, privacy leaks, or confusing copy.feedback-gate: expose user decisions and comments, then hand them todesign-feedback-collector.developer-view: reveal technical task ids, skill routes, dependencies, and artifact paths without changing customer copy.
Required Workflow
- Read references/data-source-contract.md.
- Read references/decision-framework.md.
- Read references/safety-boundaries.md.
- In
bootstrapmode, do not wait forTASK-PLAN.md. Immediately createproject-request.json, appendworkflow-log.jsonl, build a minimalprogress-state.json, renderagent-progress-screen.html, and open it in the browser. In the local project implementation, usebootstrap_progress_screen.py --open-browser. - After the bootstrap screen exists, route to
task-plan-v2-orchestratorto create canonicalTASK-PLAN.md. - In
initorupdatemode, locate canonicalTASK-PLAN.md. If no canonical task plan exists and bootstrap has not run, run bootstrap first, then route totask-plan-v2-orchestrator. - Build or update
progress-state.jsonfrom canonical task-plan fields, reports, artifacts, feedback state, and sanitized wiki decisions. - If a declared journey exists, include
journey_alignmentfrom the journey registry and route skip/rework/block decisions throughworkflow-compliance-supervisor. - Render
agent-progress-screen.htmlas a derived view. Do not edit HTML as the only state change. - In task-plan-derived
initmode, open the rendered HTML in the browser immediately after creation. In the local project implementation, pass--open-browsertorender_progress_screen.py. Inupdatemode, open it only when the user asks or is actively reviewing. - For user choices, comments, approvals, or rejections, route durable capture to
design-feedback-collector. - For large multi-session projects, route accepted decisions to
project-wiki-managerafter sanitization. - Validate consistency before claiming the progress screen is ready.
What ships with it
5 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.
- 8d ago First seen · 117 lines · 110 tokens per session scan A d12cce1091ef
agent-progress-visualizer 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 110 tokens to every session and 1,593 once invoked, about $0.0006 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.
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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.