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.
npx skills add sipyourdrink-ltd/bernstein --skill bernstein-statusgit 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/skills/sipyourdrink-ltd/bernstein/bernstein-status)<a href="https://agentmods.dev/skills/sipyourdrink-ltd/bernstein/bernstein-status"><img src="https://agentmods.dev/badge/skills/sipyourdrink-ltd/bernstein/bernstein-status.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.00052 | $0.00367 |
| Opus 5 | $0.00026 | $0.00183 |
| Sonnet 5 | $0.00010 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
bernstein-status 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.
What it actually says
Bernstein Status
Show the current state of the Bernstein orchestrator.
When to Use
- User asks "what's the status?" or "how's the build going?"
- User wants to see active agents, open tasks, or costs
- User asks about progress, failures, or alerts
- User wants a quick overview of the orchestration run
Instructions
- Run
scripts/status.shto fetch the full dashboard data from the Bernstein API. - Parse the JSON output and present a clear summary:
Summary format
## Bernstein Status
**Agents:** {active_count} active | **Tasks:** {done}/{total} done | **Cost:** ${cost_usd}
### Active Agents
| Agent | Role | Model | Runtime | Task | Cost |
|-------|------|-------|---------|------|------|
| {id} | {role} | {model} | {runtime}m | {task_title} | ${cost} |
### Tasks
- {open} open, {claimed} claimed, {done} done, {failed} failed
### Alerts
- {alert messages if any}
### Cost Breakdown
- Budget: ${budget} | Spent: ${spent} ({percentage}%)
- Per model: {breakdown}
- If the API is not reachable, tell the user to start Bernstein with
bernstein run. - Highlight any alerts (failed tasks, budget warnings, stalled agents) prominently.
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.
- 8d ago First seen · 50 lines · 52 tokens per session scan A d46626bb0f3a
bernstein-status is a skill published in the GitHub repository sipyourdrink-ltd/bernstein (1,119 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 367 once invoked, about $0.0003 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
Agent Audit Trail
Append-only, hash-chained audit log for AI agents. Records agent actions, tool calls, decisions, and external writes with provenance, timestamps, and sha256 chain integrity. Designed for compliance with EU AI Act Article 12 automatic event recording requirements for high-risk AI systems.
akf-trust-metadata
The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing.
ai-research-reproduction
Rigor Reproduce compatible skill slug for README-first deep learning repository reproduction. Use when the user wants an end-to-end, minimal-trustworthy flow that reads the repository first, selects the smallest documented inference or evaluation target, coordinates intake, setup, trusted execution, optional trusted…
Supply Chain Security
Software supply chain security — SBOM generation and analysis, dependency confusion and typosquatting detection, malicious package indicators, CI/CD pipeline hardening, and artifact provenance/signing (SLSA, Sigstore).
explore-run
Rigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subset validation, short-cycle guess-and-check, batch sweeps, idle-GPU search, or quick transfer-learning trials, with…
explore-code
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together…