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/okwinds/miscellany/bf-skillsruntime-devnpx skills add okwinds/miscellany --skill bf-skillsruntime-devgit clone --depth 1 https://github.com/okwinds/miscellanyWhat 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.00132 | $0.02661 |
| Opus 5 | $0.00066 | $0.01331 |
| Sonnet 5 | $0.00026 | $0.00532 |
| Haiku 4.5 | $0.00013 | $0.00266 |
Grade A, and why
bf-skillsruntime-dev 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skills Runtime SDK 业务开发指南
核心原则:
- 离线优先:先让
FakeChatBackend跑通最小闭环,再接真模型 - Skills-First:角色能力先沉淀成
SKILL.md,编排层只负责组合 - 证据优先:副作用必须能在 WAL / approvals / tool events 中回放
- 双轨协作:固定角色用
Coordinator,动态子任务用 collab primitives
事实快照:
- 当前技能按 2026-04-02 / SDK 0.1.11 校对
- 本技能只引用当前目录内的
references/与scripts/ - 如果你发现仓库事实再次变化,先更新本技能的本地 references,再继续使用
开场动作
- 先定位本地仓库根目录,不要默认联网克隆。
- 优先确认当前环境是否已经安装
skills-runtime-sdk;未安装时再用本地仓库做 editable install。 - 先选开发形态,再决定读哪份本地 reference:
- 单 agent + 工具:看
references/recipes-index.md - Skills 注入 / references / actions:看
references/config-templates.md - 多 agent / 动态协作:看
references/api-cheatsheet.md+references/recipes-index.md - 安全 / 审批 / 沙箱:看
references/safety-and-sandbox.md - 回归 / 验证 / 证据:看
references/testing-strategy.md
- 单 agent + 工具:看
本地环境准备
如果已知仓库根目录,记为 REPO_ROOT:
export REPO_ROOT=/abs/path/to/skills-runtime-sdk
安装 SDK 二选一:
# 方式 A:开发模式安装(推荐)
pip install -e "$REPO_ROOT/packages/skills-runtime-sdk-python"
# 方式 B:临时 PYTHONPATH(不安装)
export PYTHONPATH="$REPO_ROOT/packages/skills-runtime-sdk-python/src"
CLI 两种入口都可用:
skills-runtime-sdk --help
python3 -m skills_runtime.cli.main --help
快速开始
1) 生成业务骨架
python3 scripts/scaffold_app.py my-app --out . --with-skills
# 预览:加 --dry-run
# 覆盖:加 --force
默认生成:
run.pyconfig/runtime.yamlskills/tests/
2) 离线跑通
python3 run.py --workspace-root /tmp/my-app --mode offline
3) 最小回归
pytest -q tests
如果你正在本仓内开发,再跑仓库门禁:
bash scripts/pytest.sh
pytest -q packages/skills-runtime-sdk-python/tests/test_examples_smoke.py
推荐导入与运行骨架
最小 Agent
from pathlib import Path
from skills_runtime.agent import Agent
from skills_runtime.llm.fake import FakeChatBackend, FakeChatCall
from skills_runtime.llm.chat_sse import ChatStreamEvent
agent = Agent(
workspace_root=Path("/tmp/demo").resolve(),
backend=FakeChatBackend(calls=[
FakeChatCall(events=[
ChatStreamEvent(type="text_delta", text="EXAMPLE_OK: done."),
ChatStreamEvent(type="completed", finish_reason="stop"),
])
]),
)
result = agent.run("完成任务")
print(result.status, result.final_output, result.wal_locator)
What ships with it
9 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.
- README.md 2.6 KB
- README.zh-CN.md 2.7 KB
- references/api-cheatsheet.md 6.4 KB
- references/config-templates.md 2.8 KB
- references/recipes-index.md 3.1 KB
- references/repo-reading-map.md 2.8 KB
- references/safety-and-sandbox.md 2.5 KB
- references/testing-strategy.md 2.9 KB
- scripts/scaffold_app.py 6.6 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 · 313 lines · 132 tokens per session scan A 033c2fcbeb64
bf-skillsruntime-dev is a skill published in the GitHub repository okwinds/miscellany (50 stars, last pushed 3mo ago), licensed MIT. It adds 132 tokens to every session and 2,661 once invoked, about $0.0007 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…