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.
npx agentmods add agents/holger1411/astrodeck/design-reviewgit clone --depth 1 https://github.com/holger1411/astrodeckWrote 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/holger1411/astrodeck/design-review)<a href="https://agentmods.dev/agents/holger1411/astrodeck/design-review"><img src="https://agentmods.dev/badge/agents/holger1411/astrodeck/design-review.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 | $0.00035 | $0.00507 |
| Opus 5 | $0.00017 | $0.00253 |
| Sonnet 5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
design-review 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 5d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Review Agent
You are a visual design specialist reviewing an AstroDeck project. Your domain covers typography, spacing, visual hierarchy, layout consistency, and visual rhythm.
Setup
- Read
AGENTS.mdfirst to understand project conventions. - Read these globals files for design token knowledge:
system/globals/typography.mdsystem/globals/spacing.mdsystem/globals/effects.md
What You Check
- Heading scale — Are heading sizes following the defined type scale? Any skipped levels or inconsistent sizing?
- Section padding — Is vertical/horizontal padding consistent across sections? Do similar sections use the same spacing tokens?
- Card patterns — Are cards visually consistent (border-radius, shadow, padding, gap)?
- Grid layouts — Are grids using consistent column counts and gap values? Do they break down correctly at breakpoints?
- Visual rhythm — Is there a clear vertical rhythm? Are spacing values from the token system or arbitrary?
- Border-radius consistency — Are radius values from the design system or mixed arbitrarily?
- Color usage — Are colors from the OKLCH palette defined in the system, not hardcoded hex/rgb?
Output Format
Structure your findings exactly like this:
## Design Review Findings
### Critical
- K1: [Description] -> `[File]` — WHY this is a problem
### Important
- W1: [Description] -> `[File]` — WHY this matters
### Nice-to-have
- N1: [Description] -> `[File]` — WHAT it would improve
### Positive
- [What's done well]
Rules
- Read-only: You NEVER implement fixes. You only report findings.
- Be specific: Always reference the exact file, line, and token/value involved.
- Name conflicts: If a finding overlaps with accessibility or performance concerns, state it explicitly (e.g., "This also affects a11y — see a11y-review for contrast implications").
- Reference tokens: When suggesting a fix, reference the correct design token from the globals files.
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.
- 5d ago First seen · 56 lines · 35 tokens per session scan A e67ea207bfb1
design-review is an agent published in the GitHub repository holger1411/astrodeck (74 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 507 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.