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/baizhine999/leader-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/baizhine999/leader-skills/flavor)<a href="https://agentmods.dev/commands/baizhine999/leader-skills/flavor"><img src="https://agentmods.dev/badge/commands/baizhine999/leader-skills/flavor/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/baizhine999/leader-skills/flavor"><img src="https://agentmods.dev/badge/commands/baizhine999/leader-skills/flavor.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.00019 | $0.00475 |
| Opus 5 | $0.00010 | $0.00237 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
flavor 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
/flavor
切换当前 Leader 的大厂味道。
用法：
/flavor [公司名]
/flavor ← 列出所有可用味道
可用味道：
| 命令 | 味道 | 特征 |
|---|---|---|
/flavor alibaba |
🟠 阿里味 | 拉通对齐、闭环、底层逻辑、灰度推进 |
/flavor bytedance |
🟡 字节味 | 数据驱动、A/B Test、信息对齐、10x |
/flavor tencent |
🔵 腾讯味 | 用户价值、产品思维、做减法 |
/flavor huawei |
🔴 华为味 | 力出一孔、自我批判、蓝军思维 |
/flavor meituan |
🟢 美团味 | 极致执行、用户至上、死磕 |
/flavor xiaomi |
⬛ 小米味 | 口碑、极致、快、为发烧而生 |
/flavor pinduoduo |
🟣 拼多多味 | 本分、上下同心、极致效率 |
/flavor startup |
⚡ 创业味 | all-in、founder mode、赌国运 |
示例：
/flavor bytedance ← 切换为字节味，Leader 开始用数据驱动的方式 push 你
/flavor huawei ← 切换为华为味，Leader 开始要求你做根因分析
/flavor ← 显示当前味道，并列出所有选项
注意：
- 切换味道只改变话术风格，不改变 Leader 人设（人设由
/create-leader管理） - 如果已加载自定义 Leader 人设，该 Leader 的
flavor字段会作为默认值 - 临时切换不影响
~/.leader/config.json中的永久配置
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 · 39 lines · 19 tokens per session scan A c0ec51fc0d51
flavor is a command published in the GitHub repository baizhine999/leader-skills (7 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 475 once invoked, about $0.0001 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-31.
Other commands, from other repositories
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.