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 commands/yezannnnn/agentgroup/stylegit clone --depth 1 https://github.com/yezannnnn/agentGroupWrote 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/yezannnnn/agentgroup/style)<a href="https://agentmods.dev/commands/yezannnnn/agentgroup/style"><img src="https://agentmods.dev/badge/commands/yezannnnn/agentgroup/style.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.00000 | $0.00642 |
| Opus 5 | $0.00000 | $0.00321 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
style 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.
What it actually says
/style - 风格提取
根据参考图片提取设计风格，生成设计规范
使用方式
/style [图片路径或描述]
/style 参考这张图的风格
/style 简约现代风格
执行步骤
1. 分析参考
- 如果是图片：分析视觉元素
- 如果是描述：理解风格关键词
2. 提取设计元素
颜色分析
## 颜色提取
### 主色调
| 颜色 | 色值 | 使用场景 | 占比 |
|------|------|----------|------|
| 品牌蓝 | #1890FF | 按钮、强调 | 20% |
| 深灰 | #333333 | 主要文字 | 30% |
| 浅灰 | #F5F5F5 | 背景 | 40% |
### 辅助色
| 颜色 | 色值 | 使用场景 |
|------|------|----------|
| 成功 | #52C41A | 成功状态 |
| 警告 | #FAAD14 | 警告提示 |
| 错误 | #FF4D4F | 错误状态 |
字体分析
## 字体提取
| 层级 | 字号 | 字重 | 行高 | 用途 |
|------|------|------|------|------|
| H1 | 28px | 600 | 1.4 | 页面标题 |
| H2 | 20px | 500 | 1.4 | 区块标题 |
| Body | 14px | 400 | 1.6 | 正文 |
| Caption | 12px | 400 | 1.4 | 辅助文字 |
圆角/阴影
## 形状与效果
| 元素 | 圆角 | 阴影 |
|------|------|------|
| 卡片 | 8px | 0 2px 8px rgba(0,0,0,0.1) |
| 按钮 | 4px | none |
| 输入框 | 4px | none |
| 弹窗 | 12px | 0 4px 16px rgba(0,0,0,0.15) |
3. 输出风格规范
存储到 ../shared/designs/style-guide.md
4. 应用建议
说明如何将此风格应用到具体页面
常见风格关键词
| 风格 | 特征 |
|---|---|
| 简约现代 | 大量留白、扁平化、无衬线字体 |
| 科技感 | 深色背景、渐变、光效 |
| 温暖亲和 | 暖色调、圆角、插画 |
| 专业商务 | 冷色调、规整布局、严谨 |
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 · 79 lines · 0 tokens per session scan A 40959bf3a932
style is a command published in the GitHub repository yezannnnn/agentGroup (149 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 642 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.