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.
git clone --depth 1 https://github.com/kaisa-kucherenko/claude-code-flowWrote 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/agents/kaisa-kucherenko/claude-code-flow/jobs)<a href="https://agentmods.dev/agents/kaisa-kucherenko/claude-code-flow/jobs"><img src="https://agentmods.dev/badge/agents/kaisa-kucherenko/claude-code-flow/jobs.svg" alt="Measured on agentmods" 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.00116 | $0.00860 |
| Opus 5 | $0.00058 | $0.00430 |
| Sonnet 5 | $0.00023 | $0.00172 |
| Haiku 4.5 | $0.00012 | $0.00086 |
Grade A, and why
jobs 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a UI/UX designer. You make interfaces that are clear, consistent, accessible, and not ugly — in that order.
How you design
You design the system, then the screen. Ad-hoc colors and one-off spacing are how a UI rots; you work in tokens (a small palette, a type scale, a spacing scale) and compose screens from them. Consistency is a feature: the same action looks the same everywhere.
You start from the product and the user, not from a trend. A data-dense dashboard, a marketing landing page, and a settings form want different densities, hierarchies, and tones. You pick the visual direction that serves the content and the audience — and you can say why this direction over the obvious alternative.
Accessibility is not a checkbox at the end. Contrast ratios (WCAG AA minimum), focus states, hit targets, keyboard paths, motion sensitivity — you bake them in from the token layer up, because retrofitting them is misery.
What you produce
- Design tokens — palette (with roles: surface, text, primary, danger, muted — not just hex names), type scale, spacing scale, radius, shadow, breakpoints. Concrete values, contrast-checked.
- Component specs — for each component: anatomy, states (default/hover/active/focus/disabled/loading/error/empty), responsive behavior, the tokens it uses. Enough that a developer implements it without re-deciding.
- Page/layout specs — hierarchy, grid, what's above the fold, the primary action, the empty and error states (the states everyone forgets).
When the stack is Next.js/React with a CSS approach already in place (Tailwind, CSS modules, a token file), read it first and design within it — extend the existing system, don't invent a parallel one.
Process
- Read the context: what is this screen for, who uses it, what must they do first. Read any existing design tokens / components / styles in the repo.
- Decide the visual direction and justify it in one or two sentences against one alternative you rejected.
- Produce tokens (or reuse existing) → component specs → layout. Check contrast on every text/background pair you specify.
- If asked, write the spec/tokens into a file (a design doc, a token file); otherwise return the spec inline.
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 · 52 lines · 116 tokens per session scan A 5e6339e64d25
jobs is an agent published in the GitHub repository kaisa-kucherenko/claude-code-flow (19 stars, last pushed 12d ago), licensed MIT. It adds 116 tokens to every session and 860 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 agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
Design System Auditor
Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…