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 rules/sipyourdrink-ltd/bernstein/bernstein-contextgit 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.00399 | $0.00399 |
| Opus 5 | $0.00199 | $0.00199 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
bernstein-context 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
Bernstein Orchestrator Context
You are working in a project managed by Bernstein, a deterministic orchestrator for
CLI coding agents. Bernstein runs at http://127.0.0.1:8052 and coordinates parallel
CLI coding agents, one git worktree per task. There is no model in its coordination
loop, so the same plan replays to a byte-identical task graph.
Key concepts
- Tasks have states:
open→claimed→in_progress→done|failed|cancelled|blocked - Agents are short-lived (1-3 tasks each), spawned per task, isolated in git worktrees
- Roles: backend, frontend, qa, security, devops, docs - each agent specializes
- Quality gates: every task goes through lint, type-check, and test verification before completion
- Cost tracking: real-time per-model, per-agent spend with budget enforcement
State lives in files
.sdd/directory contains all orchestrator state (backlog, runtime, metrics, config).sdd/backlog/has task YAML files- Agents are spawned fresh per task - no persistent memory
When you see Bernstein-related requests
Use the /bernstein-status, /bernstein-create-task, /bernstein-approve, or /bernstein-cost skills
to interact with the orchestrator API at http://127.0.0.1:8052.
API base URL
The Bernstein API runs at http://127.0.0.1:8052 by default.
Set the BERNSTEIN_API_URL environment variable to override.
Set BERNSTEIN_API_TOKEN for authenticated setups.
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 First seen · 37 lines · 399 tokens per session scan A 589684571676
bernstein-context is a cursor rule published in the GitHub repository sipyourdrink-ltd/bernstein (1,038 stars, last pushed yesterday), licensed Apache-2.0. It adds 399 tokens to every session, about $0.0020 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 cursor rules, from other repositories
mcp-tools
MCP tool implementation pattern and structure.
sprint-planning
BMAD BMM Agent: sprint-planning.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.