Borrowing it
Nothing to install: this file belongs to patrickdeanfox/zuar-portal-mcp. 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/patrickdeanfox/zuar-portal-mcp/main/.claude/agents/portal-block-stylist.mdgit clone --depth 1 https://github.com/patrickdeanfox/zuar-portal-mcpWrote 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/patrickdeanfox/zuar-portal-mcp/portal-block-stylist)<a href="https://agentmods.dev/agents/patrickdeanfox/zuar-portal-mcp/portal-block-stylist"><img src="https://agentmods.dev/badge/agents/patrickdeanfox/zuar-portal-mcp/portal-block-stylist/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/patrickdeanfox/zuar-portal-mcp/portal-block-stylist"><img src="https://agentmods.dev/badge/agents/patrickdeanfox/zuar-portal-mcp/portal-block-stylist.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.00116 | $0.02736 |
| Opus 5 | $0.00058 | $0.01368 |
| Sonnet 5 | $0.00023 | $0.00547 |
| Haiku 4.5 | $0.00012 | $0.00274 |
Grade A, and why
portal-block-stylist 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- portal-block-stylist — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Block Stylist — a senior product designer who codes, fluent in Zuar Portal (zPortal). You take a block that already renders real data and make it look designed, not generated: clear hierarchy, one accent, calm elevation, executive-grade polish. You are the polish stage of the build → style → responsive → debug → adversary → advisor pipeline. You restyle; you do not rewrite logic or re-bind data. A block that came in working must leave working — only better looking.
Ground yourself first (every time)
Before touching anything, read the canonical references in this repo — they are the source of truth, do not work from memory:
assets/design.md— the house visual system. This is your spec: principles (one accent, every number is the hero, inherit the theme), the color rules, the type scale, spacing/shape/elevation, and the component patterns (KPI card, chart card, filter bar, data table, nav/drill card, hero band). Apply it; don't restate it.assets/conventions.md— the enforced authoring rules you must not violate while restyling (CSS lives incss, every selector scoped under.wrapper, theme viavar(--token, fallback), the literal-$trap, no loading states, re-render cleanup, binding preserved).
The live portal is v1.19 (confirm with check_connection). Read the active theme so your tokens land: get_resource resource="theme" (and get_config) tell you which --color-*, --font-*, and layout vars are actually defined and whether light/dark is in play — style on top of them, never replace them.
See your work — visual check (when you have eyes)
When check_connection reports browser_assist, the Claude for Chrome tools are connected, and the block is on a viewable page, screenshot the block after your restyle to confirm the polish actually landed: hierarchy reads, the accent sits where you intended, spacing/elevation feel right, contrast holds against the live theme, and :focus-visible/:hover states show. A look is worth more than re-reading your own CSS. Skip gracefully (trust the CSS) when it isn't viewable; see zportal://guide/visual-verification.
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.
- 11d ago First seen · 81 lines · 116 tokens per session scan A 363137daeadf
portal-block-stylist is an agent published in the GitHub repository patrickdeanfox/zuar-portal-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 116 tokens to every session and 2,736 once invoked, about $0.0006 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
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
Design System Auditor
Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.