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/bilibilinpx skills add sigcli/sigcli --skill bilibiligit clone --depth 1 https://github.com/sigcli/sigcliWhat 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.00120 | $0.02965 |
| Opus 5 | $0.00060 | $0.01483 |
| Sonnet 5 | $0.00024 | $0.00593 |
| Haiku 4.5 | $0.00012 | $0.00297 |
Grade A, and why
bilibili 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 3d 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bilibili
Browse trending videos, view video details, read comments, search content, view user profiles, and interact with Bilibili (B站).
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 this step.
sig status bilibili 2>&1
Check the JSON output fields configured and valid:
configured: false→ run Provider Setup below. Do NOT proceed without completing it.valid: false(but configured: true) → runsig login bilibili, then re-check.valid: true→ detect proxy (see below), then execute the user's request.
Provider Setup
- Read
<SKILL_DIR>/references/provider-config.yaml - Append the provider block to
~/.sig/config.yamlunderproviders: - Ask the user: "Do you need a proxy to access this site?" — if yes, add
networkProxy: <url>under the provider in config.yaml - Run
sig login bilibili(with--network-proxy <url>if proxy was specified) - Verify: run
sig status bilibiliagain — must showvalid: truebefore proceeding
Proxy Detection (after provider is valid)
grep -A15 "^\s*bilibili:" ~/.sig/config.yaml | grep networkProxy | awk '{print $2}'
If this outputs a URL, prefix ALL python3 commands with HTTPS_PROXY=<url> HTTP_PROXY=<url>.
If using socks5, convert to socks5h for python (e.g. socks5://... → socks5h://...).
If empty, no proxy needed.
Running Scripts
All scripts require setup to be completed first (see above).
Read operations — use sig run to inject cookie (enables authenticated features):
sig run bilibili -- bash -c 'python3 <SKILL_DIR>/scripts/bilibili_hot.py --cookie "$SIG_BILIBILI_COOKIE" --limit 10'
Write operations — require sig run (cookie is mandatory):
sig run bilibili -- bash -c 'python3 <SKILL_DIR>/scripts/bilibili_like.py --cookie "$SIG_BILIBILI_COOKIE" --aid 123456'
What ships with it
30 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 468 B
- scripts/bilibili_client.py 6.7 KB runs code
- scripts/bilibili_coin.py 1.8 KB runs code
- scripts/bilibili_comments.py 2.3 KB runs code
- scripts/bilibili_dynamic.py 3.0 KB runs code
- scripts/bilibili_favorite.py 2.7 KB runs code
- scripts/bilibili_history.py 3.2 KB runs code
- scripts/bilibili_hot.py 1.6 KB runs code
- scripts/bilibili_like.py 1.8 KB runs code
- scripts/bilibili_me.py 1.9 KB runs code
- scripts/bilibili_popular.py 1.7 KB runs code
- scripts/bilibili_ranking.py 2.0 KB runs code
- scripts/bilibili_search.py 3.7 KB runs code
- scripts/bilibili_subtitle.py 4.1 KB runs code
- scripts/bilibili_user.py 2.6 KB runs code
- scripts/bilibili_video.py 1.3 KB runs code
- tests/test_bilibili_coin.py 1.8 KB runs code
- tests/test_bilibili_comments.py 3.4 KB runs code
- tests/test_bilibili_dynamic.py 2.9 KB runs code
- tests/test_bilibili_favorite.py 2.1 KB runs code
- tests/test_bilibili_history.py 2.3 KB runs code
- tests/test_bilibili_hot.py 2.7 KB runs code
- tests/test_bilibili_like.py 1.8 KB runs code
- tests/test_bilibili_me.py 1.8 KB runs code
- tests/test_bilibili_popular.py 2.3 KB runs code
- tests/test_bilibili_ranking.py 3.1 KB runs code
- tests/test_bilibili_search.py 3.8 KB runs code
- tests/test_bilibili_subtitle.py 3.7 KB runs code
- tests/test_bilibili_user.py 2.9 KB runs code
- tests/test_bilibili_video.py 2.5 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.
- 3d ago First seen · 288 lines · 120 tokens per session scan A 2948fca52190
bilibili is a skill published in the GitHub repository sigcli/sigcli (286 stars, last pushed 9d ago), licensed MIT. It adds 120 tokens to every session and 2,965 once invoked, about $0.0006 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-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…