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 guoliang1114-boop/AriaAI --skill post-merger-integrationgit clone --depth 1 https://github.com/guoliang1114-boop/AriaAIWrote 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/guoliang1114-boop/ariaai/post-merger-integration)<a href="https://agentmods.dev/skills/guoliang1114-boop/ariaai/post-merger-integration"><img src="https://agentmods.dev/badge/skills/guoliang1114-boop/ariaai/post-merger-integration/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/guoliang1114-boop/ariaai/post-merger-integration"><img src="https://agentmods.dev/badge/skills/guoliang1114-boop/ariaai/post-merger-integration.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.00039 | $0.02766 |
| Opus 5 | $0.00019 | $0.01383 |
| Sonnet 5 | $0.00008 | $0.00553 |
| Haiku 4.5 | $0.00004 | $0.00277 |
Grade A, and why
post-merger-integration 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.
How it starts
The opening of the file, as written. The whole thing — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
并购后整合（PMI）规划
When To Use
- 交易签约后至交割前的整合准备工作
- 交割日（Day 1）的运营连续性保障
- 交割后100天的关键整合行动
- 长期组织、系统、文化整合推进
- 协同效应的追踪和实现
Tools
- PMI项目管理工具（甘特图、RACI矩阵）
- 协同效应追踪模板
- 文化评估工具（Hofstede/OCAI）
- 系统集成评估矩阵
- 沟通计划模板
Framework
5-Phase PMI Methodology
Phase 1: Pre-Close Preparation（交割前准备）
- 整合管理办公室（IMO）组建
- Day 1清单编制
- 沟通策略制定
- 关键人才识别
- IT系统评估
- 法律和监管审批
Phase 2: Day 1 Execution（交割日执行）
- 员工沟通（全员信、Town Hall）
- 客户/供应商通知
- 系统访问权限切换
- 品牌/标识变更
- 管理层任命公告
- 法律实体变更登记
Phase 3: First 100 Days（百日冲刺）
- 速赢项目（Quick Wins）执行
- 组织架构方案确定
- 关键流程对接
- 系统整合第一阶段
- 文化融合活动启动
- 协同效应项目启动
Phase 4: Full Integration（全面整合）
- 组织架构调整落地
- 系统全面整合
- 流程标准化
- 供应链优化
- 人才梯队建设
- 文化融合深化
Phase 5: Optimization（持续优化）
- 协同效应达成评估
- 持续改进机制
- 最佳实践推广
- 整合项目收尾
- 经验教训总结
McKinsey PMI Key Success Factors
- Speed：快速决策，避免整合疲劳
- Talent：保留关键人才，明确角色
- Synergy：聚焦高价值协同效应
- Culture：主动管理文化差异
- Communication：高频透明沟通
Workflow
1. 交割前准备（T-60至T-0）
├─ IMO组建及职责分工
├─ 整合范围和优先级确定
├─ Day 1清单编制（100+检查项）
├─ 沟通策略及材料准备
├─ 关键人才保留计划
└─ IT系统评估及切换方案
2. Day 1执行（T日）
├─ 员工沟通执行
├─ 客户/供应商通知
├─ 系统切换执行
├─ 管理层任命
└─ 运营连续性保障
3. 百日计划执行（T+1至T+100）
├─ 速赢项目清单及执行
├─ 组织架构方案设计及审批
├─ 关键流程对接
├─ 系统整合第一阶段
├─ 协同效应项目启动
└─ 周度/月度进展汇报
4. 全面整合（T+101至T+365）
├─ 组织架构调整落地
├─ 系统全面整合上线
├─ 流程标准化推进
├─ 供应链整合
└─ 文化融合项目
5. 持续优化（T+365+）
├─ 协同效应达成审计
├─ 整合项目收尾
├─ 经验教训总结
└─ 持续改进机制
Output Format
# 并购后整合（PMI）计划
## 一、整合概要
| 项目 | 内容 |
|------|------|
| 交易名称 | |
| 买方 | |
| 目标公司 | |
| 预计交割日 | |
| 整合范围 | |
| IMO负责人 | |
## 二、Day 1清单
| 序号 | 事项 | 责任人 | 状态 | 备注 |
|------|------|--------|------|------|
| 1 | CEO全员信发送 | | | |
| 2 | Town Hall会议 | | | |
| 3 | 客户通知函 | | | |
| 4 | 供应商通知 | | | |
| 5 | 系统访问权限 | | | |
| 6 | 管理层任命公告 | | | |
## 三、百日计划
| 项目 | 目标 | 负责人 | 开始 | 完成 | 状态 |
|------|------|--------|------|------|------|
| 速赢1 | | | | | |
| 速赢2 | | | | | |
| 组织架构设计 | | | | | |
| 系统整合Phase1 | | | | | |
## 四、协同效应追踪
| 协同项 | 类型 | 预期规模 | 实现路径 | 责任人 | 进展 | 达成率 |
|--------|------|----------|----------|--------|------|--------|
| | 收入/成本 | | | | | |
## 五、组织整合方案
| 维度 | 现状（买方） | 现状（标的） | 目标状态 | 整合方式 |
|------|-------------|-------------|----------|----------|
| 组织架构 | | | | |
| 关键岗位 | | | | |
| 薪酬体系 | | | | |
| 绩效管理 | | | | |
## 六、系统整合方案
| 系统 | 买方 | 标的 | 目标 | 整合策略 | 时间 |
|------|------|------|------|----------|------|
| ERP | | | | | |
| CRM | | | | | |
| HR | | | | | |
## 七、沟通计划
| 时间 | 对象 | 渠道 | 信息要点 | 负责人 |
|------|------|------|----------|--------|
| Day 1 | 全员 | 邮件+会议 | | |
| 第1周 | 客户 | 邮件+拜访 | | |
| 第1月 | 供应商 | 邮件+会议 | | |
## 八、风险及应对
| 风险 | 可能性 | 影响 | 应对措施 |
|------|--------|------|----------|
| 关键人才流失 | | | |
| 客户流失 | | | |
| 系统整合延迟 | | | |
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 · 296 lines · 39 tokens per session scan A 4d6e1e001c2c
post-merger-integration is a skill published in the GitHub repository guoliang1114-boop/AriaAI (37 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 2,766 once invoked, about $0.0002 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
os-workflow
A workflow guide for sending work from an AI Team OS project back into its task records. It explains how a lead agent and workflow agents record progress and important results.
Codex
Mission control: create tasks, assign to an agent/team, wait for human approval, worker runs in the background, accept results.
gsd-complete-milestone
Archive completed milestone and prepare for next version.
plan
PM planning workflow that gathers requirements, decomposes them into prioritized tasks, defines API contracts, and produces both a machine-readable plan and a human-readable tracker in docs/plans/.
coordinate-pro
Thorough version of coordinate - high-quality development workflow with 11 review steps out of 17.
coordinate
Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.