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/alifanov/darkflowWrote 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/commands/alifanov/darkflow/check-design)<a href="https://agentmods.dev/commands/alifanov/darkflow/check-design"><img src="https://agentmods.dev/badge/commands/alifanov/darkflow/check-design/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/commands/alifanov/darkflow/check-design"><img src="https://agentmods.dev/badge/commands/alifanov/darkflow/check-design.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.00020 | $0.01084 |
| Opus 5.5 | $0.00008 | $0.00434 |
| Sonnet 5.5 | $0.00004 | $0.00217 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
check-design 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 1mo 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The visual half of design review: what the interface looks like, how fast it paints, and
whether it survives contact with real content. Its counterpart is check-ux, which walks the
flows instead of looking at the surfaces.
Proposal-only. Findings become tasks; nothing is changed here.
Step 1 — Read project config
Load the project config (contract in .darkflow.d/claude.md → Project config). Uses: language, stagingUrl, domain.
Check against stagingUrl when it is set, otherwise domain. There is no list of key pages to
maintain: read sitemap.xml and pick the pages from it. If neither URL is set and there is no
sitemap, audit the components in the repo and say so in one line.
Step 2 — Quality
/impeccable:audit
Step 3 — UI performance
/impeccable:optimize
Step 4 — Production readiness
/impeccable:harden
Cover the visual failure modes only — text overflow at 320px, contrast, untranslated strings,
truncation with long real-world content. The behavioural ones (a flow that dead-ends on an
error, a missing empty state you can only reach by using the app) belong to check-ux.
Step 5 — Deduplicate, then file
Read every task in the project, not just this routine's own:
~/.darkflow/df task list --state all --format compact
Design, UX, performance and build audits all reach the same slow page from different angles;
filtering by --source would file it two or three times. Skip anything already tracked or
already dismissed (closed without a merged fix — rejected). Re-file only when a previously-fixed
problem has demonstrably regressed. A performance finding already covered by build-optimization
is theirs, not yours.
--source design,--status proposed- Priority:
high— broken layout, inaccessible element, missing state on a critical screen, LCP > 2.5s, CLS > 0.1medium— visual inconsistency, unclear hierarchy, spacing, measurable slowdown, large unoptimized asset- polish and nice-to-have → no task. It goes in the snapshot's Recommendations, nowhere else.
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.
- 1mo ago First seen · 128 lines · 20 tokens per session scan A 0de8102e0903
check-design is a command published in the GitHub repository alifanov/darkflow (4 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 1,084 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
theme-swap
Recolour an extracted site's design around a new brand primary. OKLCH hue rotation preserves perceptual lightness — neutrals, type, spacing, and motion stay untouched. Side-by-side HTML preview + recoloured tokens (DTCG, Tailwind, shadcn, Figma).
remix
Restyle a site in another design vocabulary — brutalist, swiss, art-deco, cyberpunk, soft-ui, or editorial. Preserves page shape, swaps the visual vocabulary.
studio
Launch the local design Studio — a live token editor over the latest extraction. Edit, preview a wall of real components, toggle dark mode, inspect motion, and export.
toh-ui
Create or edit UI components, pages, or layouts.
audit-design
Audit an existing HTML/CSS design. Deterministic checks only (contrast, fonts, colors, states, dark mode) plus a visual pass. No generation.
checklist
Generate a custom checklist for the current feature based on user requirements.