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/sigcli/sigcli/xiaohongshunpx skills add sigcli/sigcli --skill xiaohongshugit clone --depth 1 https://github.com/sigcli/sigcliWrote 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/sigcli/sigcli/xiaohongshu)<a href="https://agentmods.dev/skills/sigcli/sigcli/xiaohongshu"><img src="https://agentmods.dev/badge/skills/sigcli/sigcli/xiaohongshu.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 | $0.00135 | $0.04033 |
| Opus 5 | $0.00068 | $0.02017 |
| Sonnet 5 | $0.00027 | $0.00807 |
| Haiku 4.5 | $0.00014 | $0.00403 |
Grade A, and why
xiaohongshu scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
'curl -sL -H "Cookie: $SIG_XIAOHONGSHU_COOKIE" -H "User-Agent: Mozilla/5.0" \ How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xiaohongshu
Search notes, read note details, view comments, browse user profiles, and get the home feed from Xiaohongshu (小红书).
Skill Directory
<SKILL_DIR> is the directory containing this SKILL.md file. Determine it ONCE at the start and reuse it.
Setup (run FIRST — every time, before any operation)
You MUST complete this setup before running any script. Do NOT skip.
sig status xiaohongshu 2>&1
Check the JSON output fields configured and valid:
configured: false→ run Provider Setup below.valid: false(but configured: true) → runsig login xiaohongshu --mode visible, complete the captcha, then re-check.valid: true→ run Vendor Setup (one-time per machine), then execute the user's request.
Provider Setup
- Read
<SKILL_DIR>/references/provider-config.yaml - Append the provider block to
~/.sig/config.yamlunderproviders: - Run
sig login xiaohongshu --mode visible— a browser opens; scan the QR code with the Xiaohongshu app and complete the slider/image captcha if prompted - Verify:
sig status xiaohongshushould showvalid: true
Why the validateRule is so picky — three response shapes
/api/sns/web/unread_count is a permissive endpoint that hides a "partially expired cookie" state behind what looks like a successful response. The provider's validateRule is built specifically to reject it:
| State | /api/sns/web/unread_count returns |
Detected as |
|---|---|---|
| Healthy cookie | {code:0, success:true, data:{unread_count:N, likes:N, ...}} |
✅ valid |
| Cookie partially expired | {code:0, success:true, data:{}} |
❌ rejected by Object.keys(data).length > 0 |
| Cookie fully expired / logged out | {code:-101, success:false, msg:"无登录信息"} |
❌ rejected by code === 0 |
What ships with it
29 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.
- references/provider-config.yaml 2.5 KB
- requirements.txt 60 B
- scripts/sync-vendor.sh 4.2 KB runs code
- scripts/xiaohongshu_client.py 7.3 KB runs code
- scripts/xiaohongshu_get_homefeed.py 1.6 KB runs code
- scripts/xiaohongshu_get_note_comments.py 1.3 KB runs code
- scripts/xiaohongshu_get_note_info.py 1.2 KB runs code
- scripts/xiaohongshu_get_user_info.py 1.1 KB runs code
- scripts/xiaohongshu_get_user_notes.py 1.5 KB runs code
- scripts/xiaohongshu_search_note.py 1.6 KB runs code
- vendor/__init__.py 0 B runs code
- vendor/apis/__init__.py 0 B runs code
- vendor/apis/xhs_pc_apis.py 43 KB runs code
- vendor/LICENSE 1.1 KB
- vendor/package.json 90 B
- vendor/static/xhs_a1.js 19 KB runs code
- vendor/static/xhs_main_260411.js 1107 KB runs code
- vendor/static/xhs_rap.js 435 KB runs code
- vendor/static/xhs_websectiga_env.js 4.6 KB runs code
- vendor/static/xhs_xray_pack1.js 3775 KB runs code
- vendor/static/xhs_xray_pack2.js 1964 KB runs code
- vendor/static/xhs_xray.js 18 KB runs code
- vendor/UPSTREAM.md 749 B
- vendor/xhs_utils/__init__.py 0 B runs code
- vendor/xhs_utils/common_util.py 3.8 KB runs code
- vendor/xhs_utils/cookie_util.py 267 B runs code
- vendor/xhs_utils/data_util.py 12 KB runs code
- vendor/xhs_utils/http_util.py 21 B runs code
- vendor/xhs_utils/xhs_util.py 5.0 KB runs code
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.
- 4d ago First seen · 284 lines · 135 tokens per session scan A 1c4737029a23
xiaohongshu is a skill published in the GitHub repository sigcli/sigcli (286 stars, last pushed 10d ago), licensed MIT. It adds 135 tokens to every session and 4,033 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…