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.
git clone --depth 1 https://github.com/jiushiwon/wg-skillsWrote 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/commands/jiushiwon/wg-skills/scenario)<a href="https://agentmods.dev/commands/jiushiwon/wg-skills/scenario"><img src="https://agentmods.dev/badge/commands/jiushiwon/wg-skills/scenario/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/commands/jiushiwon/wg-skills/scenario"><img src="https://agentmods.dev/badge/commands/jiushiwon/wg-skills/scenario.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.00000 | $0.00857 |
| Opus 5 | $0.00000 | $0.00428 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
scenario 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 10d 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
scenario — 场景方案
输出指定场景的完整设计基线（布局 / 组件 / 交互 / Token 偏向 / 推荐调色板）。
用法
scenario <type> [--depth overview|detailed] [--compare]
支持的场景
mobile-responsive / pc-corporate / admin-dashboard / landing-marketing / docs-site / fintech-app / mobile-native / threejs-3d
参数
| 参数 | 说明 | 默认 |
|---|---|---|
<type> |
必填，场景名 | — |
--depth |
输出详细度 | detailed |
--compare |
与其他场景对比 | 否 |
流程
1. 加载场景基线
读取 references/scenarios/<type>.md，输出结构化方案。
2. 推荐品牌
按场景默认品牌映射：
| 场景 | 默认品牌 | 备选 |
|---|---|---|
| mobile-responsive | 冷调极简 | 原生移动 |
| pc-corporate | 赤琥金 | 创意广告 |
| admin-dashboard | 2B 灰蓝 | 数据深色 |
| landing-marketing | 暖色商务 | 创意广告 |
| docs-site | 文档清爽 | 冷调极简 |
| fintech-app | 金融稳重 | 2B 灰蓝 |
| mobile-native | 原生移动 | — |
| threejs-3d | 3D 沉浸 | 数据深色 |
3. 输出基线
输出格式
# 场景方案 — <type>
> 详细度：detailed
---
## 一句话定位
（场景描述 + 典型用途）
## 适用 / 不适用
**适用**：
- ...
**不适用**：
- ...
## 核心组件
| 组件 | 说明 |
|------|------|
| ... | ... |
## 布局基线
### 移动端 / 桌面 / 横屏
```css
.layout { ... }
关键 Token 偏向
--space-section: var(--space-16); /* 64px */
--radius-button: var(--radius-md);
...
推荐调色板
- XX — 主推
- YY — 备选
关键交互
- ...
- ...
反模式
- ❌ ...
- ❌ ...
验证清单
- ...
- ...
## `--compare` 模式
对比 2-3 个场景的差异：
```markdown
# 场景对比
| 维度 | mobile-responsive | pc-corporate | admin-dashboard |
|------|-------------------|--------------|-----------------|
| 触摸目标 | ≥44pt | ≥44pt | ≥32px |
| 字号下限 | 16px | 14px | 12px |
| 圆角 | 12-16px | 8-12px | 2-4px |
| 阴影 | 弱 | 中 | 克制 |
| 动效 | 平台一致 | 戏剧 | 极简 |
| 主导航 | Bottom Nav | Top Nav | Sidebar |
用途
- 决策阶段：评估哪个场景适合你的项目
- 设计阶段：作为方案模板
- 评审阶段：作为标准对比基线
- 学习：了解不同场景的设计哲学
示例
# 查看营销落地页场景
scenario landing-marketing
# 详细查看管理端
scenario admin-dashboard --depth detailed
# 对比 3 个场景
scenario admin-dashboard pc-corporate mobile-responsive --compare
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.
- 10d ago First seen · 146 lines · 0 tokens per session scan A 7f0a0c36de2f
scenario is a command published in the GitHub repository jiushiwon/wg-skills (98 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 857 tokens. 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 commands, from other repositories
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
team-ui
Orchestrate UI/UX design team.
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.