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/sipyourdrink-ltd/bernstein/bernstein-runnpx skills add sipyourdrink-ltd/bernstein --skill bernstein-rungit clone --depth 1 https://github.com/sipyourdrink-ltd/bernsteinWhat 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.00075 | $0.00668 |
| Opus 5 | $0.00037 | $0.00334 |
| Sonnet 5 | $0.00015 | $0.00134 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
bernstein-run 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 yesterday.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run a verified multi-agent goal
Bernstein is a deterministic multi-agent orchestrator for CLI coding agents. This skill wraps the three-step operator loop: submit a goal, monitor progress, and verify the finished run against its Merkle-chained lineage journal and HMAC audit chain.
Prerequisites
bernsteinon PATH (pip install bernsteinoruv tool install bernstein).- Run commands from the project root (the directory holding
.sdd/after the first run). - First-time setup:
bernstein initscaffolds config and templates.
Workflow
1. Submit
bernstein run -g "<goal>"
- The goal is a plain-English description of what to build or fix.
- Bernstein plans tasks, assigns roles (backend, frontend, qa, security, devops), and spawns agents in isolated git worktrees.
- Preview without spending:
bernstein run --dry-run -g "<goal>".
2. Monitor
bernstein status
bernstein cost
statusshows task summary and agent health.costshows the spend so far against configured budgets.
3. Verify
bernstein lineage verify <run_id>
bernstein audit verify
lineage verifyrecomputes the run's Merkle hash chain and every HMAC tag; exit 0 means the chain is intact and non-empty.audit verifychecks the HMAC audit chain and Merkle tree across the whole workspace; run it before trusting or shipping the result.
Report the run as complete only when both verifications exit 0.
Verifying this skill's own install
Installs of this skill are receipt-backed. To confirm bernstein is on PATH
and the bundled skill asset resolves in this session:
bernstein skills package show
To prove the skill content the session is driving matches what was installed:
bernstein skills package verify --dest <path-to-this-skill-directory>
Exit 0 means the installed tree's content address matches a receipt
anchored in the lineage spine and audit chain. These two commands are the
self-check contract the multi-host conformance sweep replays per agent host
(bernstein skills package conformance).
What ships with it
1 file 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.
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.
- yesterday First seen · 91 lines · 75 tokens per session scan A eb3798b7b841
bernstein-run is a skill published in the GitHub repository sipyourdrink-ltd/bernstein (1,038 stars, last pushed today), licensed Apache-2.0. It adds 75 tokens to every session and 668 once invoked, about $0.0004 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
bug-triage
Triage bugs reported in chat/issues, search for duplicates, file or update GitHub issues with full context, and push fix PRs.
ao-desktop-dev
Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR branches for local UI review; and diagnose stale Electron processes, port conflicts, or preload bridge mismatches. Use whenever asked to run, open, show, or visually…
using-ao
Catalog of the AO (Agent Orchestrator) ao CLI: spawning workers, managing sessions and projects, sending messages, controlling the shared browser, previewing pages, and daemon control. Use when using the ao CLI, spawning workers, or managing AO sessions in an AO workspace.
agent-reach
MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X / 搜搜 X / 看看大家怎么评价 X / X 上有什么讨论 / research this topic。 Also MUST USE when user mentions any platform or shares any URL/链接: 小红书/xiaohongshu/xhs, Twitter/推特/X, B站/bilibili, Reddit, Facebook, Instagram…
skill-audit
Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review.
skill-context-detection
Auto-detect work context (Dev vs Knowledge) — use to tailor workflows based on current task type.