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 resolvergit 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/resolver)<a href="https://agentmods.dev/skills/sipyourdrink-ltd/bernstein/resolver"><img src="https://agentmods.dev/badge/skills/sipyourdrink-ltd/bernstein/resolver/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/sipyourdrink-ltd/bernstein/resolver"><img src="https://agentmods.dev/badge/skills/sipyourdrink-ltd/bernstein/resolver.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00284 |
| Opus 5.5 | $0.00004 | $0.00114 |
| Sonnet 5.5 | $0.00002 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
resolver 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 1mo 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
Merge Conflict Resolver Skill
You resolve git merge conflicts between concurrent agent branches.
Specialization
- Reading both sides of a merge conflict to understand intent.
- Determining which changes to keep, combine, or rewrite.
- Preserving correctness from both branches.
- Ensuring the resolved code compiles, passes types, and maintains tests.
Work style
- Read the conflict markers and surrounding context for each file.
- Understand what each side was trying to accomplish.
- Resolve by combining both intents where possible; pick one side only when they are truly incompatible.
- After resolving all conflicts, run any available tests to verify.
- Stage resolved files and commit.
Rules
- Only modify files listed in your task's
owned_files(the conflicting files). - Never discard changes silently - if you drop one side, explain why in the commit message.
- Prefer combining both sides over picking a winner.
- If a conflict is ambiguous and cannot be safely resolved, mark the task as failed with a clear explanation.
- Do not refactor, optimize, or "improve" code beyond what is needed to resolve the conflict.
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.
- 1mo ago First seen · 39 lines · 11 tokens per session scan A cfa773d3cae7
resolver is a skill published in the GitHub repository sipyourdrink-ltd/bernstein (1,328 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 284 once invoked, about $0.0000 per session on Opus 5.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
resolve-merge-conflicts
Resolve Git merge conflicts in a Calkit project, including dvc.lock, stage run records, and pipeline outputs. Use when the user invokes /calkit:resolve-merge-conflicts, asks to merge a branch, or a merge, pull, or rebase stopped with conflicts.
commit
Skill "commit" from markmhendrickson/neotoma, covering commit, parameter detection and routing, check if parameter provided, single submodule commit workflow and all submodules commit workflow.
process_prs
Use this skill to work the open PR queue end-to-end: assess merge readiness, run security gates, selectively request Claude Opus review on substantial PRs, merge eligible PRs, and hand off release PRs to /release.
create-release
Skill "create-release" from markmhendrickson/neotoma, covering create new release, when to use, prerequisites, command execution and step 1: load documentation.
create_pr
Open a high-quality pull request with a standardized description (Problems / Solutions / UX improvements / Documentation / Test plan / Breaking changes), the changeguardrailsrules.md pre-PR checklist enforced, and thorough functional-change documentation under docs/ surfaced via the docs server and docs site. Use this…
publish
Skill "publish" from markmhendrickson/neotoma, covering publish, release numbering strategy, parameter detection and routing, check if parameter provided and submodule publish workflow.