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/jpage-skill-syncnpx skills add code2rich/agentwaker-xiaohongshu-operator --skill jpage-skill-syncgit 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/jpage-skill-sync)<a href="https://agentmods.dev/skills/code2rich/agentwaker-xiaohongshu-operator/jpage-skill-sync"><img src="https://agentmods.dev/badge/skills/code2rich/agentwaker-xiaohongshu-operator/jpage-skill-sync.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.00061 | $0.00622 |
| Opus 5 | $0.00030 | $0.00311 |
| Sonnet 5 | $0.00012 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
jpage-skill-sync 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JPage skill sync
Purpose
Fetch, inspect, and synchronize JPage-provided skills into the Xiaohongshu Operator skill area when the user configures a valid JPage base URL and token.
Trigger Conditions
Use this skill when the user asks to:
- Add JPage skills under the Xiaohongshu Operator.
- Download the server-side JPage skill.
- Refresh local JPage skill instructions from the configured JPage service.
- Compare local JPage skill instructions with the remote server version.
Required Inputs
- JPage base URL.
- JPage token or token URL setup path.
- Target skill name, usually
jpage. - Confirmation before overwriting any local skill files.
Workflow
- Check the active configuration without printing secrets:
jpage whoamijpage skills ls
- Inspect the remote skill:
jpage skills get jpage
- Download into a temporary file first:
jpage skills download jpage --out /tmp/jpage-skill.md
- Review the downloaded content for scope, sensitive data, and conflicts with this role.
- Store the reviewed upstream text under
jpage-official/references/only after confirmation. Never overwrite the role-scopedjpage-official/SKILL.mdwrapper with a broad upstream trigger. - Update the wrapper or
jpage-publishingonly when a verified upstream mechanic changes, preserving the Xiaohongshu scope and approval rules. - Update
xiaohongshu-operator-skills/SKILL.mdandagent-soul/PROFILE.yamlonly when the role-visible capability actually changes.
Approval Gates
Approval is required before:
- Replacing an existing upstream reference or changing the role-scoped wrapper.
- Adding remote content that changes this role's permissions.
- Using token URL flows that create or rotate credentials.
- Committing any generated skill content.
Failure Handling
- If the server is unavailable, record the configured base URL and retry command.
- If authentication fails, ask for token setup instructions rather than storing secrets in the repository.
- If the remote skill is broader than Xiaohongshu operations, keep only the relevant JPage publishing workflow and document what was excluded.
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 · 70 lines · 61 tokens per session scan A e7bb61b6779a
jpage-skill-sync is a skill published in the GitHub repository code2rich/agentwaker-xiaohongshu-operator (5 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 622 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…