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/writing-specs/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/writing-specs)<a href="https://agentmods.dev/skills/whiteguo233/openbiliclaw/writing-specs"><img src="https://agentmods.dev/badge/skills/whiteguo233/openbiliclaw/writing-specs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/whiteguo233/openbiliclaw/writing-specs"><img src="https://agentmods.dev/badge/skills/whiteguo233/openbiliclaw/writing-specs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 108 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00020 | $0.01072 |
| Opus 5 | $0.00010 | $0.00536 |
| Sonnet 5 | $0.00004 | $0.00214 |
| Haiku 4.5 | $0.00002 | $0.00107 |
Grade A, and why
writing-specs 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 11d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Specs and Plans
Produce an authoritative design spec and an executable implementation plan before changing code. Resolve every placeholder against the live repository.
Name and commit the pair first
Create both documents with the same dated slug:
docs/plans/YYYY-MM-DD-<slug>-spec.mddocs/plans/YYYY-MM-DD-<slug>-plan.md
Commit the pair as docs: add <feature> spec and plan before implementation. Do not mix code
into this docs-first commit.
SPEC skeleton
# <Feature> Spec — <measurable outcome>
**Created:** YYYY-MM-DD
**Scope:** <affected behavior, modules, and integrations>
**Out of scope:** <explicit non-goals>
## Goal
State the current cost or failure, quantified target outcomes, and the exact commands that
verify them.
## Design invariants (MUST hold in every phase)
1. **<Invariant name>:** <falsifiable rule and verification surface>.
2. **<Invariant name>:** <falsifiable rule and verification surface>.
## Current diagnosis
### D1. <Observed problem>
Record evidence at `path/to/file.py:line`; distinguish confirmed facts from hypotheses.
### D2. <Observed problem>
Record the caller, data flow, failure mode, and existing test coverage with `file:line` evidence.
## Priority classification
| Phase | Content | Tier | Why |
| --- | --- | --- | --- |
| 0 | <gate or prerequisite> | **MUST** | <risk it controls> |
| 1 | <main change> | RECOMMENDED | <measured leverage> |
List dependencies, then group work into **Wave A**, **Wave B**, and later waves by risk and
dependency. State what can ship independently and where work may safely stop.
## Phase designs
### Phase 0 — <name>
Define interfaces, algorithms, error behavior, tests, rollout, and numeric acceptance gates.
## Expected impact
| Lever | Measured effect |
| --- | --- |
| <phase> | <quantified result> |
## Documentation obligations
List every module doc, changelog, architecture diagram, CLI/config reference, installer doc,
and README surface triggered by the design.
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.
- 11d ago First seen · 140 lines · 20 tokens per session scan A 921856c728a2
writing-specs is a skill published in the GitHub repository whiteguo233/OpenBiliClaw (3,278 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,072 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
duckduckgo-search
Free keyless web, news, and image search via ddgs.
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…