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 agentmods add skills/antdigital-ai/agentic-ui/component-agentic-layoutnpx skills add antdigital-ai/agentic-ui --skill component-agentic-layoutgit clone --depth 1 https://github.com/antdigital-ai/agentic-uiWrote 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/antdigital-ai/agentic-ui/component-agentic-layout)<a href="https://agentmods.dev/skills/antdigital-ai/agentic-ui/component-agentic-layout"><img src="https://agentmods.dev/badge/skills/antdigital-ai/agentic-ui/component-agentic-layout.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 | $0.00057 | $0.01972 |
| Opus 5 | $0.00028 | $0.00986 |
| Sonnet 5 | $0.00011 | $0.00394 |
| Haiku 4.5 | $0.00006 | $0.00197 |
Grade A, and why
component-agentic-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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgenticLayout 组件开发
智能体应用主布局：左-中-右三栏 + 头部，用于应用外壳与侧栏布局。修改布局或头部时，按本技能内的 API 与规范直接实现，无需再查源码。
组件 API（自包含）
AgenticLayoutProps
| 属性 | 说明 | 类型 | 默认 |
|---|---|---|---|
left |
左侧内容 | ReactNode | - |
center |
中间内容（必填） | ReactNode | - |
right |
右侧内容 | ReactNode | - |
header |
头部配置，见下 | LayoutHeaderConfig | - |
style |
自定义样式，会透传到根节点（可含 minHeight 等） |
React.CSSProperties | - |
className |
自定义类名，与根节点 prefixCls、hashId 一起拼接 |
string | - |
leftWidth |
左侧宽度（px） | number | 256 |
rightWidth |
右侧宽度（px），可被用户拖拽改变，会受最小/最大限制 | number | 540 |
minHeight |
最小高度（类型已声明，实现上可用 style.minHeight 覆盖样式默认值） |
string | number | - |
children |
子元素（兼容用，内容建议用 center） |
ReactNode | - |
说明：根节点最小高度由样式固定为 600px；需自定义时传 style={{ minHeight: '...' }}。当前未从 props 的 minHeight 读到根节点，与类型保持一致即可。
LayoutHeaderConfig（头部配置）
| 属性 | 说明 | 类型 | 默认 |
|---|---|---|---|
title |
标题，支持文本或 React 节点 | ReactNode | 'AI 助手' |
showShare |
是否显示分享按钮 | boolean | false |
leftCollapsible |
左侧是否可折叠（未传时由 AgenticLayout 按是否有 left 推断） |
boolean | - |
rightCollapsible |
右侧是否可折叠（未传时由 AgenticLayout 按是否有 right 推断） |
boolean | - |
leftCollapsed |
左侧折叠状态（受控） | boolean | - |
rightCollapsed |
右侧折叠状态（受控） | boolean | - |
leftDefaultCollapsed |
左侧默认折叠（非受控） | boolean | false |
rightDefaultCollapsed |
右侧默认折叠（非受控） | boolean | false |
onLeftCollapse |
左侧折叠回调 | (collapsed: boolean) => void | - |
onRightCollapse |
右侧折叠回调 | (collapsed: boolean) => void | - |
onShare |
分享点击 | () => void | - |
leftExtra |
头部左侧额外内容，渲染在标题同侧 | ReactNode | - |
rightExtra |
头部右侧额外内容，渲染在分享/折叠按钮同侧 | ReactNode | - |
className |
头部根节点自定义类名 | string | - |
折叠状态：有 leftCollapsed/rightCollapsed 时为受控；否则用 leftDefaultCollapsed/rightDefaultCollapsed 作初始值，由内部 useMergedState + onLeftCollapse/onRightCollapse 更新。LayoutHeader 内部用 I18n 的 locale['chatFlow.collapseLeft']、locale['chatFlow.collapseRight']、locale['chatFlow.share'] 等做文案与 aria-label。
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.
- 4d ago First seen · 100 lines · 57 tokens per session scan A 514b99b60798
component-agentic-layout is a skill published in the GitHub repository antdigital-ai/agentic-ui (224 stars, last pushed 22d ago), licensed MIT. It adds 57 tokens to every session and 1,972 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…