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 agentmods add skills/code2rich/agentwaker-xiaohongshu-operator/content-planningnpx skills add code2rich/agentwaker-xiaohongshu-operator --skill content-planninggit clone --depth 1 https://github.com/code2rich/agentwaker-xiaohongshu-operatorWrote 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/code2rich/agentwaker-xiaohongshu-operator/content-planning)<a href="https://agentmods.dev/skills/code2rich/agentwaker-xiaohongshu-operator/content-planning"><img src="https://agentmods.dev/badge/skills/code2rich/agentwaker-xiaohongshu-operator/content-planning.svg" alt="Measured on agentmods" 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.00055 | $0.00380 |
| Opus 5 | $0.00028 | $0.00190 |
| Sonnet 5 | $0.00011 | $0.00076 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
content-planning 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 6d 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
Content Planning
Purpose
Build Xiaohongshu content calendars, topic clusters, audience segments, cadence plans, and campaign angle maps.
Trigger Conditions
Use this skill when the user asks for a publishing plan, content calendar, account positioning plan, campaign plan, or topic system.
Required Inputs
- Account or brand positioning.
- Target audience.
- Content goal.
- Time range or cadence expectation.
- Available assets, products, or service context.
Workflow
- Clarify goal, audience, content pillars, and constraints.
- Define topic clusters and note formats.
- Map each note idea to audience intent, hook, asset need, and CTA.
- Set cadence and sequencing.
- Mark assumptions and required assets.
Outputs
- Content calendar.
- Topic cluster map.
- Note idea backlog.
- Asset and image brief list.
- Risks and next actions.
Approval Gates
No approval is needed for planning. Approval is required before scheduling, publishing, or interacting from the account.
Failure Handling
If context is missing, produce a provisional plan and mark assumptions.
Handoff Rules
- Hand planned covers, first images, carousel cards, explanatory diagrams, evidence visuals, and routine flat visual templates to
xiaohongshu-visuals. - Hand Xiaohongshu-supporting static JPage artifacts to
jpage-publishing. - Hand only custom-coded interactive demos, pages, components, or reusable visual tools to FrontDeveloper with the audience intent, approved copy, current target constraints, evidence needs, and acceptance checks.
What ships with it
1 file 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.
- 6d ago First seen · 53 lines · 55 tokens per session scan A 6d8e83f1c789
content-planning is a skill published in the GitHub repository code2rich/agentwaker-xiaohongshu-operator (5 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 380 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…