error-flow

error-flow is a command for coding agents from Owl-Listener/designer-skills. It costs 18 tokens per session (215 once invoked), scanned A, original, MIT.

A command for planning what happens when a product feature fails, from preventing the problem to helping the user recover.

In plain words
What is it for?
Use it to specify error conditions, user feedback, state changes, prevention measures, and recovery paths.
Why use it?
It prevents error messages from becoming dead ends by covering detection, explanation, retries, and recovery.

Command

Part of the interaction-design plugin — 22 skills, 5 commands shipped together

About the project

Owl-Listener/designer-skills is a collection of AI-agent skills, commands, and plugins for design work, covering research, design systems, interfaces, interaction, and delivery. Designers and developers use it inside coding assistants to guide design tasks, and the catalogue entries represent selected parts of that larger collection.

Owl-Listener/designer-skills · 2,502 stars · on GitHub

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 commands/owl-listener/designer-skills/error-flow
Clone the repo
git clone --depth 1 https://github.com/Owl-Listener/designer-skills

Or install interaction-design, the plugin that ships this one along with the rest of its 22 skills, 5 commands.

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 error-flow

README.md
[![agentmods](https://agentmods.dev/badge/commands/owl-listener/designer-skills/error-flow.svg)](https://agentmods.dev/commands/owl-listener/designer-skills/error-flow)
Your own site
<a href="https://agentmods.dev/commands/owl-listener/designer-skills/error-flow"><img src="https://agentmods.dev/badge/commands/owl-listener/designer-skills/error-flow.svg" alt="Measured on agentmods" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 215 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.00018 $0.00215
Opus 5 $0.00009 $0.00108
Sonnet 5 $0.00004 $0.00043
Haiku 4.5 $0.00002 $0.00021

Measured yesterday against content hash e6568bb320c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

error-flow 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 yesterday.

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.

interaction-design/commands/error-flow.md · 17 lines

What it actually says

/error-flow

Design complete error handling for a feature.

Steps

  1. Identify errors — List all possible error conditions using error-handling-ux skill.
  2. Prevention — Design prevention measures using error-handling-ux skill.
  3. State modeling — Map error states using state-machine skill.
  4. Feedback — Design error communication using feedback-patterns skill.
  5. Recovery — Design recovery paths using error-handling-ux skill.
  6. Loading — Handle timeout and retry states using loading-states skill.

Output

Error handling specification with error inventory, prevention measures, state diagram, error messages, recovery flows, and retry strategies. Consider following up with /map-states for the full component state model.

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. yesterday First seen · 17 lines · 18 tokens per session scan A e6568bb320c6

Subscribe to this mod's changes

error-flow is a command published in the GitHub repository Owl-Listener/designer-skills (2,502 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 215 once invoked, about $0.0001 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.