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 chuwu57/Chuwu-PR-OS --skill pr-contingency-plangit clone --depth 1 https://github.com/chuwu57/Chuwu-PR-OSWrote 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/chuwu57/chuwu-pr-os/pr-contingency-plan)<a href="https://agentmods.dev/skills/chuwu57/chuwu-pr-os/pr-contingency-plan"><img src="https://agentmods.dev/badge/skills/chuwu57/chuwu-pr-os/pr-contingency-plan/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/chuwu57/chuwu-pr-os/pr-contingency-plan"><img src="https://agentmods.dev/badge/skills/chuwu57/chuwu-pr-os/pr-contingency-plan.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.00103 | $0.01968 |
| Opus 5.5 | $0.00041 | $0.00787 |
| Sonnet 5.5 | $0.00021 | $0.00394 |
| Haiku 4.5 | $0.00010 | $0.00197 |
Grade A, and why
pr-contingency-plan 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 13d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
公关预案
归属说明：本Skill由初五维护，属于初五的个人Skill体系。分享或再分发时请保留本归属说明及已有来源、作者和许可声明。
定位
预案不是追求零风险。零风险通常不存在。
预案要做的是：在动作上线前，把可能消耗信任、引发误解、被对手放大、被媒体截图、被监管追问的点提前拆开，然后判断哪些要改动作，哪些备口径，哪些只监测。
最终产出三样东西：
- 这次最可能被挑什么。
- 被挑时能公开署名怎么答。
- 上线前哪些地方必须改、必须备、只需看。
知识调用
默认按本文件完成预案。遇到高风险动作、责任归因、爆料格式、平台传播、利益相关方复杂或组织取舍问题时，读取 references/knowledge-map.md。
知识调用后仍要落到三类处理：必须改动作、必须备口径、只需监测。不要用理论解释替代上线前清单。
先定标
不要一上来扫风险。先判断这次动作服务什么：
- 曝光。
- 信任。
- 品类教育。
- 风险修复。
- 行业地位。
- 政策合法性。
- 渠道或用户承接。
不同目标能承受的争议不同。短期声量不能透支长期信任。
路由
命中高频场景时，按需读取对应reference；其中步骤为模块菜单，按本次动作、素材和决策范围选择，不自动扩展成完整研究项目：
| 场景 | 读取 |
|---|---|
| 品牌出现在综艺、纪录片、直播、联名等内容中 | references/content-placement.md |
| 产品上新、升级、换配方、换包装 | references/product-launch.md |
| 明星、达人、IP、KOL 合作 | references/spokesperson-fandom.md |
| 换厂、换渠道、规则调整、服务政策变化 | references/change-issue.md |
如果不属于四类，不要硬套。走通用流程即可。
通用流程
定标 → 对象研究 → 历史与同类回查 → 六格风险扫描 → 外部攻击推演 → 口径与处置 → 收口
一次动作涉及多类时，只补充新增且相关的模块，共享事实与检查复用，输出收成一份预案。
六格风险扫描
六个角度作为内部扫描清单保留，每个角度记录检查状态与依据范围。正文优先呈现重点风险和影响上线判断的缺口，不为填满六格强行制造风险：
- 动作本身：定价、承诺、姿态、价值立场是否招打。
- 产品或内容交付：产品、服务、内容、活动是否有失败模式。
- 相关方：用户、员工、合作方、渠道、特定群体是否会觉得被冒犯或受损。
- 规则环境：法律、监管、平台规则、行业规范有没有红线。
- 历史旧伤：品牌、行业、合作对象过去的问题会不会被翻出。
- 关联方与对手：代言人、供应商、平台、竞品、恶意账号是否会把风险传导过来。
每个维度使用以下状态，不能用一句「暂无风险」合并：
- 已发现风险：当前材料支持具体失败路径，写明风险与依据；尚未发生的后果仍标为预测。
- 已检查未发现：已检查相关材料，在本次范围内未发现具体风险；说明检查了什么及范围限制，不代表风险为零。
- 证据不足：缺少会影响判断的材料，列明缺口、由谁补证以及补证前建议。未检查、拿不到资料或只有单方口头保证，不能转成「已检查未发现」。
- 不适用：该维度与本次动作无实质关联，简述原因；资料缺失不属于不适用。
每项重点风险需连接触发条件、具体依据、可能后果与判断边界、建议动作、责任人与责任缺口。责任人未提供时标「待指定」及所需职责，不虚构姓名或内部承诺。证据缺口同时说明补证结果怎样改变建议；仅在缺口会改变上线安全性或关键承诺时，把补证设为前置条件。
外部攻击与质疑推演是情景假设。说明什么条件下可能出现、依据来自当前材料还是可比案例；不得把想象中的媒体质疑、竞对动作、监管反应或传播量级写成已发生或确定会发生。
处理分三类
对已有依据的风险和必要的条件化处置，落到三类之一。证据不足的项目先明确补证动作与决策条件，不用分类掩盖未知：
- 必须改动作：已确认产品、承诺、合作或利益安排存在实质问题，说明要改什么及依据。区分真实交付缺陷、宣传超过证据和单纯缺少凭证：分别评估修正交付、收窄或撤回主张、补证；不要因材料缺失直接要求改产品。
- 必须备口径：动作可以做，但外部会追问，需要可公开、可核验、能一致执行的回答。
- 只需监测：风险存在但不值得主动解释，设监测点和升级红线即可。
口径标准：
- 能公开署名。
- 对得上事实。
- 不扩大承诺。
- 不把计划写成结果。
- 不用情绪安抚替代事实解释。
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago Changed · +1 lines c1d17d250a0f
- 1mo ago Changed · +19 lines · +6 tokens per session 7a30446e12f0
- 1mo ago First seen · 120 lines · 97 tokens per session scan A 4a05d44b2d67
pr-contingency-plan is a skill published in the GitHub repository chuwu57/Chuwu-PR-OS (84 stars, last pushed 13d ago), licensed MIT. It adds 103 tokens to every session and 1,968 once invoked, about $0.0004 per session on Opus 5.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
goal
Use when the user invokes /goal, asks for goal mode, designs an agent loop, or starts long-horizon autonomous work that should be clarified into a concrete, verifiable objective before execution.
launch-loop-strategy
Use when planning a practical launch loop for a feature, product update, template, prompt, skill, integration, beta, or release with a known launch date, especially when the user needs channels, content angles, a posting schedule, community distribution, replies, DMs, and follow-up remixes.
marketing-growth
Use when planning product marketing, writing marketing copy, designing pricing tiers, building programmatic SEO pages, optimizing on-page SEO, managing social media accounts and publishing queues, planning social media calendars, running Twitter automation, conducting Google Trends research, brainstorming brand/domain…
launch-strategy
Use when planning a product launch, feature release, waitlist, beta, public announcement, relaunch, Product Hunt-style push, repeated feature launch system, launch-week checklist, or multi-channel GTM rollout.
x-article-writer
Use when writing or rewriting longform X/Twitter articles, X Articles, founder essays, launch essays, growth teardowns, product breakdowns, build-in-public stories, or sharp startup takes that need X-native hooks, tone, pacing, and structure. Use for X Articles and long posts, not blog SEO posts, lifecycle emails, or…
copywriting
Use when writing or rewriting website copy: homepages, landing pages, pricing pages, product pages, feature pages, hero sections, headlines, subheads, CTAs, value propositions, taglines, and above-the-fold messaging. Do not use for email sequences, blog posts, longform X articles, or platform-specific ad copy.