Borrowing it
Nothing to install: this file belongs to existential-birds/amelia. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/existential-birds/amelia/main/.claude/commands/review-css-complexity.mdgit clone --depth 1 https://github.com/existential-birds/ameliaWrote 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/existential-birds/amelia/review-css-complexity)<a href="https://agentmods.dev/commands/existential-birds/amelia/review-css-complexity"><img src="https://agentmods.dev/badge/commands/existential-birds/amelia/review-css-complexity/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/existential-birds/amelia/review-css-complexity"><img src="https://agentmods.dev/badge/commands/existential-birds/amelia/review-css-complexity.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.00021 | $0.00384 |
| Opus 5.5 | $0.00008 | $0.00154 |
| Sonnet 5.5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
review-css-complexity 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.
What it actually says
Scan the codebase for overly complex CSS and styling patterns. Look for:
Red Flags
-
Absolute positioning with placeholders - If you see absolute positioning combined with invisible placeholder elements to maintain layout, it's probably overcomplicated. Use flexbox/grid instead.
-
Complex width/height calculations - Formulas like
width: ${(hasMore ? visibleCount + Math.min(3, hiddenCount) - 1 : visibleCount - 1) * 16 + 120}pxare a code smell. Use CSS variables or simpler layouts. -
Nested positioning contexts - Multiple layers of relative/absolute positioning that could be flattened.
-
Transform calculations - Complex
translateX/translateYcalculations when simple flexbox/grid would work. -
Manual spacing calculations - Computing gaps/offsets manually instead of using CSS gap, space-x, or margins.
What to Look For
Search for files containing:
style={{with complex JavaScript expressions- Multiple layers of
absoluteandrelativepositioning - Placeholder divs with
opacity-0used for layout - Calculations involving multiple conditional operators in inline styles
- Comments explaining complex positioning logic (if it needs explaining, it's too complex)
Good Alternatives
- Flexbox with
-space-x-*for overlapping elements - CSS Grid for complex layouts
- CSS custom properties for dynamic values
- Tailwind utility classes over inline styles
Output
For each file with issues:
- File path and line numbers
- What's overcomplicated
- Suggested simpler approach
- Estimated complexity reduction (high/medium/low priority)
Focus on dashboard/src and amelia frontend code.
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 · 45 lines · 21 tokens per session scan A 66421aeb7d8b
review-css-complexity is a command published in the GitHub repository existential-birds/amelia (21 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 384 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-30.
Other commands, from other repositories
review-artifact-comments
Works through the review comments written into a task artifact (plan or research under .ork/tasks/TASK/): lists the open ones, asks how to proceed, then replies, resolves or hands off to iterate-plan or iterate-research, and approves the artifact once nothing is open. Use when a reviewer has commented on an artifact…
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
anchors
List what each requirement tag anchors to (read-only).
mach12:issue-review
Read a GitHub issue and all comments, review the implementation plan, and present findings.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.
code-review-give
Give mode for code-review: Review someone else's code with multi-pass analysis and structured recommendations.