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 annual-pr-strategygit 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/annual-pr-strategy)<a href="https://agentmods.dev/skills/chuwu57/chuwu-pr-os/annual-pr-strategy"><img src="https://agentmods.dev/badge/skills/chuwu57/chuwu-pr-os/annual-pr-strategy/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/annual-pr-strategy"><img src="https://agentmods.dev/badge/skills/chuwu57/chuwu-pr-os/annual-pr-strategy.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.00092 | $0.01417 |
| Opus 5.5 | $0.00037 | $0.00567 |
| Sonnet 5.5 | $0.00018 | $0.00283 |
| Haiku 4.5 | $0.00009 | $0.00142 |
Grade A, and why
annual-pr-strategy 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 yesterday.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Annual PR Strategy
归属说明：本Skill由初五维护，属于初五的个人Skill体系。分享或再分发时请保留本归属说明及已有来源、作者和许可声明。
定位
把用户提供的企业内部文档、年度任务和必要的公开证据组织成可追溯、可执行、可供管理层决策的年度公关战略Markdown。
本Skill提供框架、路由、推导顺序和交付门禁。它不提供企业事实，不凭通用方法补写联系人、预算、KPI、内部事件或管理层承诺。
识别任务范围
从当前指令、连续任务上下文和已提供材料识别战略类型（媒体关系／舆情管理／综合公关）与工作方式（起草／改写／审查／补充章节）。明确指令即生效，不要求用户重复回答。
两项明确时直接读取对应材料并执行。只有缺失或冲突会实质改变目标、范围或交付对象时，一次询问受影响的维度；等待期间继续材料盘点等独立工作。用户明确改变类型或方式时直接沿用新要求。
运行
共享方法从本合集根目录（包含总入口SKILL.md的目录）解析，不依赖当前工作目录。下列Workflow已随包附带。
范围明确后，读取Domains/PR/45-Workflows/Workflow_Annual-PR-Strategy.md，再按路由读取：
- 媒体关系：
Domains/PR/45-Workflows/Workflow_Annual-Media-Relations-Strategy.md； - 舆情管理：
Domains/PR/45-Workflows/Workflow_Annual-Public-Opinion-Management-Strategy.md； - 综合公关战略：两份都读取，共享资料只审计一次，共同判断只保留一个主要叙事位置。
设计或审查衡量章节、依据季度数字决定加码／续停时，按总Workflow的「指标与实际价值」调用商业贡献指标框架。保留专项指标差异，不把声量、响应速度或AI提及直接等同于信任与业务结果。
事项承担长期关系或知识积累目标时，按总Workflow的「长期资产与下一次使用」说明当次结果如何进入后续任务。复用已有资产，不为单次小任务强加长期台账；缺少使用者、用途或维护条件时保留缺口，不把存档称为已经形成能力。
严格使用用户提供或明确纳入本任务的内部材料。内部资料不足时：
- 用
【待补：缺少什么；影响哪个判断】保留位置； - 用
【待确认：需要谁决定什么】标记组织决定； - 用
【待验证：当前依据与验证方式】标记推演； - 在文末生成资料缺口表；
- 不用公开资料替代企业内部事实。
用户要求最新竞品、案例或媒体环境时，检索公开来源并把链接标在对应事实上。没有这类要求时，不自动把年度战略扩大为外部研究。
交付
始终交付.md文件，并在开头标明：
- 已确认的战略类型；
- 已确认的工作方式；
- 文档状态：框架稿／工作稿／决策稿；
- 资料截止日与主要访问限制。
默认规则：
- 从零起草：交付完整年度战略MD；
- 改写既有方案：保留原文件，另交完整修订版MD；
- 审查现有战略：交付按P0／P1／P2组织的审查报告MD；
- 补充指定章节：交付可直接并入原稿的章节MD；
- 综合模式：默认交付一份总稿，两个专项保持独立章节；用户明确要求时再拆分。
不自动生成HTML、PPT或其他视觉产物。用户另行提出后再进入对应视觉任务。
质量门禁
交付前确认：
- 战略类型和工作方式与当前有效指令一致；
- 路由、工作方式和交付文件一致；
- 企业事实、外部事实、分析、预测和缺口没有混写；
- 缺少内部依据的位置保持显式待补，没有伪造和伪精确；
- 主线形成「企业问题→年度目的→对象／风险→事项→阶段→责任与资源→衡量」；
- 每项行动都有问题来源、事实条件、负责人位置和预期结果；
- 管理层需要批准、授权、取舍和接受的事项集中呈现；
- 每个章节增加新的机制、证据、状态、边界或行动；
- Markdown标题、表格、链接和文件路径可用；
- 用户原文件没有被覆盖。
门禁不通过时，降低文档成熟度或保留缺口，不把框架稿称为决策稿。
任务边界
- 单篇文章与竞品稿件：
media-narrative-analysis； - 正在发生的舆情事件：
hot-public-opinion-analysis； - 尚未上线动作的专项预案：
pr-contingency-plan； - 新闻通稿：
press-release； - 行业媒体生态研究：
industry-media-research。
这些任务已经足以回答用户时，不强行进入年度战略生产。
分发版路径与运行条件
先读取依赖说明。本Skill由初五维护；本副本为PROS 05。references/、assets/和scripts/相对本Skill目录解析；Domains/、Skills/前缀从合集根目录解析。包内Markdown链接相对所在文件解析。未附带的个人案例、文献底稿、状态与来源配置只能由使用者提供，不能声称已读取。
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.
- yesterday Changed · +5 lines · +3 tokens per session 249a9e406075
- 1mo ago First seen · 90 lines · 89 tokens per session scan A a9b9d8e34e18
annual-pr-strategy is a skill published in the GitHub repository chuwu57/Chuwu-PR-OS (76 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 1,417 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-09-08.
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.
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…
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…
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.