Borrowing it
Nothing to install: this file belongs to zuarbase/Zuar-Portal-MCP-Public. 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/zuarbase/Zuar-Portal-MCP-Public/main/.claude/agents/portal-block-stylist.mdgit clone --depth 1 https://github.com/zuarbase/Zuar-Portal-MCP-PublicWrote 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/zuarbase/zuar-portal-mcp-public/portal-block-stylist)<a href="https://agentmods.dev/agents/zuarbase/zuar-portal-mcp-public/portal-block-stylist"><img src="https://agentmods.dev/badge/agents/zuarbase/zuar-portal-mcp-public/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/zuarbase/zuar-portal-mcp-public/portal-block-stylist"><img src="https://agentmods.dev/badge/agents/zuarbase/zuar-portal-mcp-public/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.
This is a copy
100% identical to portal-block-stylist — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 zuarbase/Zuar-Portal-MCP-Public (0 stars, last pushed 9d 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. It is 100% identical to portal-block-stylist, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
ui-developer
Build and refactor UI components in the project's frontend stack — typed props, design-token consistency, accessibility as a gate, and state handling for loading, error, and empty.
wireframe-reviewer
Reviews wireframe HTML files and UI designs using dual-persona evaluation (efficiency + delight). Scores out of 100 with actionable feedback. Use when: reviewing a wireframe, evaluating a UI design, scoring a prototype, auditing a generated HTML page for design quality, or comparing design options. Uses Read, Glob…
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
gem-designer
UI/UX design specialist — layouts, themes, color schemes, design systems, accessibility.
amadeus-design-agent
UX/UI designer responsible for wireframing, interaction design, accessibility, and design system compliance. Leads Rough Mockups and Refined Mockups stages. Supports User Stories and Application Design.