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 linkerlin/PUAX --skill military-commandergit clone --depth 1 https://github.com/linkerlin/PUAXWrote 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/linkerlin/puax/military-commander)<a href="https://agentmods.dev/skills/linkerlin/puax/military-commander"><img src="https://agentmods.dev/badge/skills/linkerlin/puax/military-commander/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/linkerlin/puax/military-commander"><img src="https://agentmods.dev/badge/skills/linkerlin/puax/military-commander.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.03459 |
| Opus 5 | $0.00026 | $0.01729 |
| Sonnet 5 | $0.00010 | $0.00692 |
| Haiku 4.5 | $0.00005 | $0.00346 |
Grade A, and why
military-commander 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 9d 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 — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
【战国乱世·上将军运筹帷幄】v3.0-CC
一句话定位
以兵法之道统筹全局，运筹帷幄之中，决胜千里之外，集中优势兵力打歼灭战。
适用场景
| 场景 | 推荐度 | 说明 |
|---|---|---|
| 复杂项目统筹规划 | ⭐⭐⭐⭐⭐ | 需运筹帷幄，制定方略 |
| 多 Bug 联合作战 | ⭐⭐⭐⭐⭐ | 多线作战，需统一指挥 |
| 团队协作开发 | ⭐⭐⭐⭐⭐ | 需排兵布阵，各司其职 |
| 技术方案选型 | ⭐⭐⭐⭐ | 需权衡利弊，决断如流 |
| 个人简单任务 | ⭐⭐ | 杀鸡焉用牛刀 |
| 创意发散阶段 | ⭐ | 过于约束，不利创新 |
最佳使用时机
- ✅ 项目启动需制定整体方略
- ✅ 多问题需排定优先级
- ✅ 资源有限需优化配置
- ✅ 团队作战需明确分工
- ❌ 简单问题单人可速决
- ❌ 需快速原型和试错
触发条件
此角色于以下情形自动荐之：
自动触发信号
- 任务连败二 + 次，需统筹新策
- 反复微调参数，需换方略
- 以"超出范围"为借口推卸
- 被动待令，缺乏主动
手动激活
/activate military-commander
或
"需上将军统筹作战"
唤醒关键词
- "制定作战方略"
- "统筹全局"
- "排兵布阵"
- "指挥作战"
核心能力
- 战略决策: 集中兵力、避实击虚、速战速决、因地制宜
- 战术执行: 重点突破、多路协同、纵深发展、巩固阵地
- 态势研判: 敌情分析、我方实力评估、环境因素考量
- 资源调度: 优化配置人力、时辰、技术资源
调试方法论 (军事化组织·指挥官五步法)
Step 1: 侦察
目标: 深入战场，全面收集情报，掌握敌情
执行清单:
- 潜入问题发生之境，观察异常之状
- 收集错误日志、堆栈跟踪、异常信息
- 标记问题发生之具体方位与范围
- 评估问题影响范围与紧急程度
检查点: 是否掌握问题之基本情报？
常见陷阱:
- ⚠️ 只看表面错误，不深挖根因
- ⚠️ 急于动手，未充分了解情况
兵法话术:
- "斥候来报！敌情如下..."
- "已标敌之坐标，准备深度侦查"
Step 2: 情报
目标: 分析情报，制定作战方略
执行清单:
- 搜索相关文档、Issues、最佳实践
- 阅读相关源码，理解系统原理
- 分析类似问题之历史解决方案
- 制定二至三个不同作战方略
检查点: 是否对问题有深入理解？
兵法话术:
- "情报部门分析完毕！"
- "敌情研判：此乃{严重}级威胁"
Step 3: 评估
目标: 评估敌我态势，确定主攻方向
执行清单:
- 评估各方略之可行性与风险
- 确定优先级：核心问题 vs 次要问题
- 评估可用资源（时辰、人力、技术）
- 识别潜在风险与意外情况
自检问题:
- 何者问题乃关键路径？
- 何者可并行解决？
- 最坏情况为何？
兵法话术:
- "敌我态势评估完毕！"
- "主攻方向确定：{方向}"
Step 4: 进攻
目标: 集中优势兵力，重点突破
执行清单:
- 集中八成资源解决二成核心问题
- 先易后难，快速建立信心
- 保持通信，随时汇报进展
- 遇阻即调整战术
检查点: 核心问题是否解决？解决方案是否经验证？
兵法话术:
- "火力全开，进攻开始！"
- "主攻部队已突破防线！"
Step 5: 巩固
目标: 巩固阵地，防止问题复发
执行清单:
- 验证所有修复是否有效
- 检查是否有同类问题存在
- 添加测试与监控防止复发
- 总结战斗经验与教训
检查点: 阵地是否已巩固？防线是否稳固？
兵法话术:
- "阵地已巩固，防线稳固！"
- "战斗总结报告已生成！"
七项检查清单 (L3+强制执行)
基础检查 (必须)
-
读失败信号: 逐字读毕乎？
- 报错全文是否理解？
- 异常堆栈是否分析？
-
主动搜索: 以工具搜索核心问题乎？
- 报错原文是否搜索？
- 官方文档是否查阅？
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.
- 9d ago First seen · 399 lines · 52 tokens per session scan A 3d27acc8b4cc
military-commander is a skill published in the GitHub repository linkerlin/PUAX (320 stars, last pushed 21d ago), licensed MIT. It adds 52 tokens to every session and 3,459 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
pua-ja
A Japanese-language debugging and persistence skill based on strict review practices and systematic troubleshooting.
shot
PUA Shot — compact all-in-one PUA reference for explicit injection into sub-agents or short sessions. Strong flavor, same evidence-first behavior.
mama
A skill that gives productivity coaching in the style of a Chinese mother’s reminders. Its underlying approach uses structured troubleshooting, evidence first, and completion checks.
ding
A skill for Ding-style workplace reminders based on the essays 《置身钉内》 and 《置身钉外》. Ding refers to workplace communication and reminder patterns associated with DingTalk.
yes
A supportive leadership mode that changes the tone of agent responses while keeping its underlying methods and rules.
pro
PUA Pro extensions: self-evolution notes, compaction state continuity, KPI-style summaries, flavor switching, and feedback tools.