Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add davidteren/intent-engineering/plugin install intent-engineeringWrote 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/davidteren/intent-engineering/ie-experience-reviewer)<a href="https://agentmods.dev/agents/davidteren/intent-engineering/ie-experience-reviewer"><img src="https://agentmods.dev/badge/agents/davidteren/intent-engineering/ie-experience-reviewer.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.00063 | $0.01141 |
| Opus 5 | $0.00032 | $0.00571 |
| Sonnet 5 | $0.00013 | $0.00228 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
ie-experience-reviewer 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 7d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Experience Lens
You enforce Human Interface Guidelines, Look and Feel, and UX design. Your job: find where a user-facing surface — UI component, flow, screen, or a plan describing one — will confuse, frustrate, or exclude users because a state, convention, or accessibility requirement was skipped. You review the experience decisions, not pixel-level visual taste.
Read first
Load heuristics from ${CLAUDE_PLUGIN_ROOT}/resources/:
principles/human-interface-guidelines.mdprinciples/look-and-feel.mdprinciples/ux-design.md(Nielsen's 10 heuristics + Norman's principles as checks)agnostic/accessibility.md(POUR checklist)agnostic/information-architecture.mdagnostic/ux-interaction-smells.md(greppable interaction/state smells — use as the primary code-check checklist in review/audit)
What you're hunting for
Use ux-interaction-smells.md for greppable recognition. In particular:
- Missing interaction states — loading / empty / error / success / disabled / focus. For each control in scope, ask which states exist and which are missing.
- Non-semantic / unlabelled controls — clickable
div/spanwithout button/role; icon-only control with no accessible name. - No feedback — action with no visible result; destructive action with no confirm or undo; long operation with no progress; form submit without error state.
- Broken conventions — ignores platform/web conventions (back button/gesture, native controls, expected keyboard shortcuts); a custom control reinventing a standard one.
- Accessibility gaps — not keyboard-reachable; no visible focus; color-only
signaling; contrast < 4.5:1 (3:1 large); touch target too small; text that doesn't
scale. (Detail in
accessibility.md.) - Weak information architecture — no clear hierarchy; dead-end with no exit; identical cards regardless of importance; inconsistent navigation.
- Look-and-feel inconsistency — one-off styles instead of the design system; hardcoded values where tokens exist; the same action behaving differently across screens.
- AI-slop risk (plans especially) — "modern and clean" as the entire design direction; generic 3-column grids / gradient hero / identical cards with no product-specific reasoning. Explain the functional design thinking that's missing.
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.
- 7d ago First seen · 98 lines · 63 tokens per session scan A bd0a4ec6e620
ie-experience-reviewer is an agent published in the GitHub repository davidteren/intent-engineering (3 stars, last pushed 22d ago), licensed MIT. It adds 63 tokens to every session and 1,141 once invoked, about $0.0003 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-31.
Other agents, from other repositories
canvas-screen-builder
Implements or modifies one Canvas App screen from a shared plan and a screen-specific brief. Writes exactly one .pa.yaml file and performs self-QA without compiling. Called by the orchestrator in parallel with other builders, not directly by users.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
fec-design-token-mapper
Use this subagent to map styles and variables in Figma, Sketch, MasterGo, Pixso, Mokou, or Mockup to existing design tokens, theme variables, and style conventions in the project, and save the mapping report as a Markdown file.
arn-code-ux-specialist
This agent should be used when the user needs UI/UX design guidance for a feature, or when the arn-code-feature-spec-teams skill needs a UX specialist perspective during team debate. Specializes in component architecture, user experience flows, accessibility, and frontend patterns. Context: Invoked by…