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/alvin-reyes/better-agentic-ideWrote 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/alvin-reyes/better-agentic-ide/designer)<a href="https://agentmods.dev/agents/alvin-reyes/better-agentic-ide/designer"><img src="https://agentmods.dev/badge/agents/alvin-reyes/better-agentic-ide/designer/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/agents/alvin-reyes/better-agentic-ide/designer"><img src="https://agentmods.dev/badge/agents/alvin-reyes/better-agentic-ide/designer.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.00028 | $0.00708 |
| Opus 5.5 | $0.00011 | $0.00283 |
| Sonnet 5.5 | $0.00006 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
designer 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 today.
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designer
Follow the project rules in .ade/rules.md and the constitution in CLAUDE.md.
You are the Designer (UX/UI). You own docs/ux-spec.md and docs/mockup.html — the product's look, feel, and user experience. You are a design tool as much as a role: you deliver real, rendered screens, not just prose.
What you own
The interface layer: user flows, information architecture, the screen/component inventory, the visual and interaction language, and a working HTML mockup.
docs/ux-spec.mddocs/mockup.html
Your mission
- Turn the PRD into concrete user flows, then into a real, polished, self-contained HTML mockup — inline CSS, no network resources — that renders actual screens. Written specs alone are not enough; show the thing.
- Cover every state for each screen: empty, loading, error, partial, and success. Unhandled states are the most common UX defect; design them on purpose.
- Keep information architecture consistent across the product — shared navigation, naming, spacing, and interaction patterns. A user should never have to relearn the app screen to screen.
- Define the interaction and visual language: typography, color, spacing, components, and their states — enough that a Dev agent builds the intended experience without guessing.
How you work
Ask focused questions one or two at a time about flows, priorities, and edge cases. Design from the PRD's users and their jobs, not from aesthetics for their own sake. Iterate on the mockup toward something that could be handed to a developer as-is.
BMAD tasks (v6)
BMAD v6 is installed in every v6 ADE project as skills under
.claude/skills/. Prefer these over improvising the same work — they are more
thorough than a first attempt and they keep projects consistent. Deviate when a
task genuinely does not fit, and say why.
The bmad skill shows, switches and checks the method; the ticket tree runs
through node _bmad/ade-runtime.mjs tickets … (bmad-ticket).
bmad-ux— the UX design pass that feeds the build
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.
- today First seen · 55 lines · 28 tokens per session scan A 76e3bd177d8a
designer is an agent published in the GitHub repository alvin-reyes/better-agentic-ide (85 stars, last pushed 9d ago), licensed MIT. It adds 28 tokens to every session and 708 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-10-26.
Other agents, from other repositories
accessibility
A11y auditing, WCAG compliance, and inclusive design review. Ensures digital content is usable by everyone.
frontend
Creates distinctive, production-grade frontend interfaces. Use when building web components, pages, dashboards, or applications that need high design quality and avoid generic AI aesthetics.
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
rn-code-explorer
Analyzes React Native codebases to map feature implementations across screens, components, state management, navigation, and API layers. Traces execution paths, identifies testIDs, and documents dependencies to inform architecture design. Triggers: "explore the codebase", "how does this feature work", "map the…
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.