OpenBiliClaw is a local, open-source AI agent that learns a person's interests and discovers content across multiple social platforms and the open web. It is for people who want personalized content recommendations with their usage data kept on their own machine.
Borrowing it
Nothing to install: this file belongs to whiteguo233/OpenBiliClaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/whiteguo233/OpenBiliClaw/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/whiteguo233/OpenBiliClawWrote 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/whiteguo233/openbiliclaw/release)<a href="https://agentmods.dev/skills/whiteguo233/openbiliclaw/release"><img src="https://agentmods.dev/badge/skills/whiteguo233/openbiliclaw/release.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00018 | $0.00662 |
| Opus 5 | $0.00009 | $0.00331 |
| Sonnet 5 | $0.00004 | $0.00132 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
release 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 8d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release OpenBiliClaw
Follow all six steps in order. Stop when any gate fails; never publish a partially verified release.
1. Run pre-flight checks
Require a clean worktree on main, pull the latest commit, and run the full test suite:
git status --short
git branch --show-current
git pull --ff-only
.venv/bin/python -m pytest -q
Do not continue until git status --short is empty and the branch is main.
2. Bump mechanical versions
Use the repository tool as the only writer for mechanical version fields:
.venv/bin/python scripts/release.py --bump X.Y.Z
When the extension version changes, include --extension X.Y.Z; the flag may also be used
alone for an extension-only release. Never hand-edit mechanical version fields. The changelog
heading and README callout content in the next steps are deliberate hand edits.
3. Update the changelog
Hand-edit the top of docs/changelog.md with ## vX.Y.Z: theme (YYYY-MM-DD) and the release's
verified changes. The final scripts/release.py --check warns if this heading is missing.
4. Replace the README callouts
Hand-edit the 📌 callouts under the recent-updates sections. Follow CLAUDE.md rule 10; the three hard limits are:
- Use at most four bullets.
- Replace the previous callout; never append another version callout.
- Keep
README.mdandREADME_EN.mdin lockstep with the same items and order.
Then verify every mechanical field and both user-facing version headers:
.venv/bin/python scripts/release.py --check
5. Commit and push tags individually
Review the release-only diff, stage only those files, and commit:
git commit -m "chore: release X.Y.Z" -- <release-paths>
Create the aggregate openbiliclaw-vX.Y.Z tag and the applicable backend-vX.Y.Z,
extension-vX.Y.Z, and desktop-vX.Y.Z channel tags. Push one tag per git push
invocation. A four-tag push previously emitted no GitHub events, leaving all four release
workflows silently dead; never combine tag refspecs in one push.
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.
- 8d ago First seen · 81 lines · 18 tokens per session scan A 1526f07dba09
release is a skill published in the GitHub repository whiteguo233/OpenBiliClaw (3,215 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 662 once invoked, about $0.0001 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
publish-site
Versioned site deploys to GitHub/Cloudflare/Netlify Pages.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
goal-issues-and-release
Clear the open issue backlog and then cut a release, in one autonomous run: use the batch-all-issues skill to resolve every open issue, then the goal-release skill to draft, merge, and see the release through publication. Never asks the user anything — every decision is made autonomously, and blockers are reported at…
goal-release
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…