dorkos: Skill for Claude Code

.agents/skills/auditing-ui/SKILL.md

auditing-ui is a skill for Claude Code, Codex from dork-labs/dorkos. It costs 115 tokens per session (6,059 once invoked), scanned A, original, MIT.

A skill that examines a website or application interface through several user-experience checks and records the findings as tracked work items. It does not change the code.

In plain words
What is it for?
Use it to audit a whole interface, a selected screen, one quality area, or changes between versions, including checks in a real browser.
Why use it?
It turns scattered interface problems into a ranked report and manageable batches of work.

Skill for Claude CodeCodex

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; mentions Claude Code; installed under .agents/ (shared by several agents).

This is dork-labs/dorkos's own configuration. It tells Claude Code and Codex how to work on dorkos itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dorkos configures →

Part of the flow plugin — 43 skills, 44 commands, 5 agents, 4 hooks shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to dork-labs/dorkos. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dork-labs/dorkos/main/.agents/skills/auditing-ui/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/dork-labs/dorkos

Made for: Claude Code, Codex.

Or install flow, the plugin that ships this one along with the rest of its 43 skills, 44 commands, 5 agents, 4 hooks.

Wrote 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.

agentmods badge for auditing-ui

README.md
[![agentmods](https://agentmods.dev/badge/skills/dork-labs/dorkos/auditing-ui/github.svg)](https://agentmods.dev/skills/dork-labs/dorkos/auditing-ui)
Your own site
<a href="https://agentmods.dev/skills/dork-labs/dorkos/auditing-ui"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/auditing-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.

agentmods 80×15 button for auditing-ui

Your own site · 80×15
<a href="https://agentmods.dev/skills/dork-labs/dorkos/auditing-ui"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/auditing-ui.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 115 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,059 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00115 $0.06059
Opus 5.5 $0.00046 $0.02424
Sonnet 5.5 $0.00023 $0.01212
Haiku 4.5 $0.00012 $0.00606

Measured today against content hash 62b88038ed6c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

auditing-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 today.

The scan reads SKILL.md. This mod also ships 8 executable files (assets/measure/focus-walk.mjs, assets/measure/guards.mjs, assets/measure/guards.test.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/auditing-ui/SKILL.md · 370 lines

How it starts

The opening of the file, as written. The whole thing — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Auditing UI

An audit reads the interface through several independent lenses at once, then merges what they saw into one ranked report and a set of PR-sized batches. It writes zero code.

The rules live in the charter, not here: audits/ui.md (domain) inherits audits/README.md (cross-domain). What passes lives in contributing/design-review.md: the numbered rules a finding cites and the floors the browser leg measures. The charter is the authority on the lens set, the lens keys, and which lens is surface-local versus whole-tree. This file is the procedure, and it is the single home for the procedure: the commands under /ui-audit:* point here rather than restating any of it.

Read the charter before every run. If audits/ui.md is missing, run /ui-audit:init first.

1. Durable state

Three things outlive any single run and live at the domain root, audits/runs/ui/:

Path What Written by
profile.md how work lands in this repo /ui-audit:init
stamps.json per-lens last-audited commit + rotation cursor run and pulse
<date>/ one run's report.md, raw/<key>.md, and its ledger when untracked run and pulse

<date> is ISO YYYY-MM-DD.

The repo profile is consulted, not decorative

Read audits/runs/ui/profile.md at the start of every run, pulse, and execute. It answers questions this procedure deliberately does not hard-code, and each answer changes behavior:

  • Landing style — a repo with no merge queue must not inherit arm-then-verify or a bare gh pr merge --auto; execute follows the profile's answer, not this repo's habits.
  • Changelog — whether a batch owes a fragment, and in what shape.
  • Isolation — worktree per batch, or something else.
  • Formatting gate — the exact command that satisfies CI, run last before every push.
  • Tracker mode — the adapter path in §5, or the markdown ledger.
  • Browser leg — the dev command and a free port, or the fact that there is none, which is what §3's degrade rule keys off.

Read the full file on GitHub · 370 lines

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. today Changed · +65 lines · +35 tokens per session 62b88038ed6c
  2. 29d ago Changed · +1 lines 9c8459d622cc
  3. 1mo ago First seen · 304 lines · 80 tokens per session scan A d4ce0eeb221d

Subscribe to this mod's changes

auditing-ui is a skill published in the GitHub repository dork-labs/dorkos (12 stars, last pushed today), licensed MIT. It adds 115 tokens to every session and 6,059 once invoked, about $0.0005 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-09-08.