Bernstein is an open-source governance layer for AI agents that applies written policies, schedules agent work deterministically, controls approvals, and records verifiable execution history. It is used to coordinate CLI coding agents and other agent workloads, including parallel runs and offline review, while the catalogue entries provide its agent workflows and controls.
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.
git clone --depth 1 https://github.com/sipyourdrink-ltd/bernsteinWrote 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/commands/sipyourdrink-ltd/bernstein/run)<a href="https://agentmods.dev/commands/sipyourdrink-ltd/bernstein/run"><img src="https://agentmods.dev/badge/commands/sipyourdrink-ltd/bernstein/run.svg" alt="Measured on agentmods" height="20"></a>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.00009 | $0.00107 |
| Opus 5 | $0.00005 | $0.00053 |
| Sonnet 5 | $0.00002 | $0.00021 |
| Haiku 4.5 | $0.00001 | $0.00011 |
Grade A, and why
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 2d 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.
What it actually says
Start an orchestration run. Bernstein decomposes the goal into tasks, spawns CLI coding agents in parallel git worktrees, verifies their output, and merges results. No model sits in the coordination loop, so replaying a plan reproduces its task graph byte-identically.
Usage: /bernstein:run $ARGUMENTS
The argument is the goal string describing what you want built or fixed. Bernstein handles task decomposition, agent assignment, and verification automatically.
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.
- 2d ago Changed 779332e55406
- 7d ago First seen · 10 lines · 9 tokens per session scan A 2dfffc8aee60
run is a command published in the GitHub repository sipyourdrink-ltd/bernstein (1,119 stars, last pushed today), licensed Apache-2.0. It adds 9 tokens to every session and 107 once invoked, about $0.0000 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 commands, from other repositories
analyze-project
Run Rigor Analyze on this repository using the current compatible slug.
szukaj
Szukaj orzeczeń po frazie/słowie kluczowym w orzeczenia.ms.gov.pl lub sn.pl. Produkuje listę wyników JSON.
status
Check the current governance status for your session, including your plan, remaining capacity, and whether the governance layer is operating normally.
receipts
View the tamper-evident receipts generated for governed actions in the current session or a specified time window.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.