workflow-audit

A systematic review of how users move through a SwiftUI app, from entry points to completed actions. SwiftUI is Apple’s framework for building app interfaces.

In plain words
What is it for?
Use it to inspect app entry points, trace user journeys, detect and rate workflow problems, check data wiring, and produce an audit report in the project.
Why use it?
It helps find screens that lead nowhere, broken navigation, incomplete promises, confusing flows, and missing connections between the interface and the underlying data.

Skill for Claude CodeCodex

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 skills/terryc21/workflow-audit/workflow-audit
Any agent
npx skills add Terryc21/workflow-audit --skill workflow-audit
Clone the repo
git clone --depth 1 https://github.com/Terryc21/workflow-audit

Made for: Claude Code, Codex.

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,598 The whole file, excluding the scripts and references it only reads on demand.
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.00059 $0.06598
Opus 5 $0.00030 $0.03299
Sonnet 5 $0.00012 $0.01320
Haiku 4.5 $0.00006 $0.00660

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

Security

Grade A, and why

workflow-audit 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 2d 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.

skills/workflow-audit/SKILL.md · 481 lines

How it starts

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

Workflow Audit Skill

Quick Ref: 5-layer UI workflow audit: discover entry points → trace flows → detect issues → evaluate UX → verify data wiring. Output: .workflow-audit/ in project root.

You are performing a systematic workflow audit on this SwiftUI application.

Rating findings. Where a layer produces findings — a confirmed problem you have read the code for — rate each one on all six dimensions in the Issue Rating Table: Urgency, Risk:Fix, Risk:NoFix, ROI, Blast Radius, and Fix Effort. A partial rating quietly drops a finding out of triage: the user is deciding what to fix before the next release, and a row missing Risk:NoFix or Blast Radius can't be weighed against the rows that have them, however real the bug is.

Layer 1 is the exception, by design. Its output is an inventory of entry points with flags for Layer 2 to investigate — hypotheses, not verified problems. Rating an unverified flag would assign urgency to something nobody has confirmed is broken, which is exactly what the Work Receipts rule exists to prevent. Layer 1 reports counts and flags; ratings begin at Layer 3 where findings are verified against source.

Quick Commands

Command Description
/workflow-audit Full 5-layer audit
/workflow-audit layer1 Discovery only — find all entry points
/workflow-audit layer2 Trace — trace critical paths
/workflow-audit layer3 Issues — detect problems across codebase
/workflow-audit layer4 Evaluate — assess user impact
/workflow-audit layer5 Data wiring — verify real data usage
/workflow-audit trace "A → B → C" Trace a specific user flow path
/workflow-audit diff Compare current findings against previous audit
/workflow-audit fix Generate fixes for found issues
/workflow-audit fix --apply-anyway Same, but auto-apply even with uncommitted changes
/workflow-audit status Show audit progress and remaining issues

Read the full file on GitHub · 481 lines

Files

What ships with it

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

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. 2d ago First seen · 481 lines · 59 tokens per session scan A 6b353eefd600

Subscribe to this mod's changes

workflow-audit is a skill published in the GitHub repository Terryc21/workflow-audit (58 stars, last pushed 5d ago), licensed Apache-2.0. It adds 59 tokens to every session and 6,598 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

roundtrip-radar

Per-journey code audit tracing data through complete user flows for bugs, data safety, performance, and round-trip completeness. Discovers workflows, audits each end-to-end, rolls up cross-cutting issues, and supports natural-language flow tracing. Triggers: "roundtrip audit", "trace user journey", "/roundtrip-radar".

Terryc21/radar-suite · 73 tokens

radar-suite

Unified entry point for the 6-skill radar family (5 companions + capstone). Routes to individual skills, runs targeted (Tier 2) or full (Tier 3) audit sequences, owns the unified ledger, and provides cross-skill operations (status, verify, ledger, link, deferred, fresh/no-fresh). Triggers: "radar suite", "full audit"…

Terryc21/radar-suite · 94 tokens

radar-suite-axis-classification

Shared axis classification framework for all radar-suite skills. Every finding must be classified as axis1 (bug), axis2 (scatter), or axis3 (dead/smelly) before emission, with mandatory coaching fields and file:line citations to existing patterns in the audited codebase. Triggers: invoked by every radar before…

Terryc21/radar-suite · 77 tokens

ui-enhancer-radar

Systematic iOS/SwiftUI UI audit with design intent interview, 14-domain analysis (including Color Audit with adaptive Color Profile, iPad Sheet Sizing caller-side audit, Button Hit Region three-factor interaction audit, and Silent Picker menu-presentation audit), element compaction, cross-view consistency checks…

Terryc21/radar-suite · 148 tokens

ui-path-radar

UI path tracer for SwiftUI/UIKit apps. 5-layer audit with 34 issue categories and 19 automated checks: discover entry points, trace flows, detect dead ends and broken promises, evaluate UX impact, verify data wiring. Supports targeted trace, diff against previous audits, and handoff to planning skills. Triggers…

Terryc21/radar-suite · 86 tokens

capstone-radar

Unified A-F grading and ship/no-ship decisions for the 6-skill radar family (5 companions + capstone). Aggregates handoffs from data-model, ui-path, roundtrip, time-bomb, and ui-enhancer; owns 5 grep-reliable domains; tracks velocity; celebrates improvements. Triggers: "capstone radar", "can I ship", "grade codebase"…

Terryc21/radar-suite · 91 tokens