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 skills add HuolalaTech/huolala-figma-mcp --skill adjust-list-groupgit clone --depth 1 https://github.com/HuolalaTech/huolala-figma-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/skills/huolalatech/huolala-figma-mcp/adjust-list-group)<a href="https://agentmods.dev/skills/huolalatech/huolala-figma-mcp/adjust-list-group"><img src="https://agentmods.dev/badge/skills/huolalatech/huolala-figma-mcp/adjust-list-group/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/skills/huolalatech/huolala-figma-mcp/adjust-list-group"><img src="https://agentmods.dev/badge/skills/huolalatech/huolala-figma-mcp/adjust-list-group.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.00038 | $0.00927 |
| Opus 5 | $0.00019 | $0.00464 |
| Sonnet 5 | $0.00008 | $0.00185 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
adjust-list-layout 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 12d 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.
What it actually says
调整列表布局层级
根据 JSON 布局描述文件识别列表控件类型（横向、纵向、网格），并自动调整 HTML 代码中的布局结构。
When to Use
- 当需要将设计稿转换后的 HTML 代码进行布局优化时
- 当 HTML 中的列表元素层级结构不合理时
- 当需要将平铺的元素转换为语义化的列表、表格或 Flex 布局时
- 当存在
vlm_result.json等布局描述文件，需要据此调整代码结构时
Instructions
参数说明
| 参数名 | 类型 | 默认值 | 说明 |
|---|---|---|---|
json_file |
string | vlm_result.json |
JSON 布局描述文件路径 |
code_file |
string | index.html |
需要调整的 HTML 代码文件路径 |
前置条件
- 检查
${json_file}是否存在（可选，不存在则跳过 JSON 相关步骤）
第 1 步：识别列表控件
从 ${json_file} 中找出列表控件，判断条件如下：
| 列表类型 | 判断条件 |
|---|---|
| 横向列表 | 子元素的 y 和 height 一致；或者两组交错 y 和 height 一致的元素交错排列 |
| 纵向列表 | 子元素的 width 和 x 坐标都一致；或者局部连续的元素 width 和 x 坐标相同，且子元素的结构相似 |
| 网格列表 | 子元素 height 相同，存在多行，同行 y 坐标相同 |
第 2 步：控件匹配
遍历列表控件，在 ${code_file} 中进行控件匹配：
- 横向列表匹配：找到
${code_file}中一个容器，其包含的文本大部分都能与横向列表元素匹配成功 - 纵向列表匹配：找到
${code_file}中一个容器，其包含的文本大部分都能与纵向列表元素匹配成功 - 网格列表匹配：将网格拆成多行，逐行文本匹配，每行中的文字大部分都能匹配成功
第 3 步：调整布局
将原始 ${code_file} 备份为 ${code_file}.backup，然后修改 ${code_file} 调整布局。
3.1 横向列表调整
| 子类型 | 处理方式 |
|---|---|
| 交错列表 | 将 ${code_file} 中相邻的交错元素用一个新容器进行包裹和分组，变成标准横向列表 |
| 带分割线列表 | 如果横向列表元素中包含垂直分割线，且分割线和其他元素间隔分布，则将分割线提取出来，剩余的元素包裹容器宽度进行等分，内部元素垂直居中 |
3.2 局部纵向列表调整
如果 ${code_file} 中的局部纵向列表元素未被包裹，用一个新容器将这些元素包裹起来。
3.3 网格列表调整
⚠️ 必须按顺序判断
如果 ${code_file} 中每一行的文本匹配到的容器都不一样，将这些容器合并成一个大的网格布局：
| 判断顺序 | 类型 | 条件 | 处理方式 |
|---|---|---|---|
| 1 | 表格 | 行列元素间距都 ≤ 2px，且同一列的元素宽度相同（误差 ≤ 1px） | 不要用flex-wrap: wrap布局，改成 <table> 结构 |
| 2 | 折行布局 | 不满足表格条件（不同列元素宽度不一致） | 采用 display: flex; flex-wrap: wrap，并计算设置 row-gap 和 column-gap |
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.
- 12d ago First seen · 74 lines · 38 tokens per session scan A 13400d95e45a
adjust-list-layout is a skill published in the GitHub repository HuolalaTech/huolala-figma-mcp (78 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 927 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 skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
waitlist-page
A simple waitlist page for collecting email addresses from people interested in a new product or early-access release.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.