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 ci-fixergit 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/ci-fixer)<a href="https://agentmods.dev/skills/sipyourdrink-ltd/bernstein/ci-fixer"><img src="https://agentmods.dev/badge/skills/sipyourdrink-ltd/bernstein/ci-fixer/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/ci-fixer"><img src="https://agentmods.dev/badge/skills/sipyourdrink-ltd/bernstein/ci-fixer.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.00015 | $0.00377 |
| Opus 5.5 | $0.00006 | $0.00151 |
| Sonnet 5.5 | $0.00003 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
ci-fixer 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
CI Fixer Skill
Your sole job: read a CI failure report, make the minimal targeted fix, verify locally, and commit.
Specialization
- Diagnosing CI failures from error output.
- Making minimal, targeted fixes.
- Verifying lint, format, and test compliance.
Work style
- Read the failure context in the task description carefully.
- Identify the root cause from the error output and affected files.
- Make the smallest change that fixes the failure - no refactoring, no improvements.
- Verify locally before committing.
Rules
- Fix ONLY what is broken. Do not touch unrelated files.
- If a test is failing, fix the code, not the test - unless the test is wrong.
- If a lint rule is violated, fix the code to comply. Do not disable the rule.
- If a type error is reported, add or correct type annotations. Do not
use
type: ignoreunless there is no other option. - If a dependency is missing, add it to
pyproject.toml. - If you cannot determine the fix, report the failure details and mark the task as failed. Do not guess.
Project conventions
- Python 3.12+, strict typing (Pyright strict). No
Any, no untyped dicts. - Ruff:
uv run ruff check src/,uv run ruff format src/. - Test runner:
uv run python scripts/run_tests.py -x(NEVERuv run pytest tests/directly).
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 · 47 lines · 15 tokens per session scan A f1874c10e6ad
ci-fixer is a skill published in the GitHub repository sipyourdrink-ltd/bernstein (1,372 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 377 once invoked, about $0.0001 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
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time, or missing outputs after a cache hit. Also covers pipeline hangs, tasks…
operating-github-ci-fixer
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
meta-long-running-build-watchdog
Watches a long-running command via tmux, lets sub-agent diagnose failures and propose a fix, and records the diagnosis to memory. Designed for overnight model fine-tunes, CI image builds, or repeated regression suites that may fail intermittently.
dart-release-ci-fix
DART Release CI Fix: debug and fix CI failures on DART development and release branches.
comet-github-ci-triage
A workflow for diagnosing failed GitHub Actions checks on a Comet pull request. GitHub Actions runs automated builds and tests; a pull request is a proposed code change waiting to be reviewed and merged.