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/orchestrationgit 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.00000 | $0.00173 |
| Opus 5 | $0.00000 | $0.00086 |
| Sonnet 5 | $0.00000 | $0.00035 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
orchestration 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 3d 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
This project uses Bernstein, a deterministic orchestrator for CLI coding agents. When working on tasks:
- State lives in
.sdd/, not in agent memory. Read files there for context. - Each agent gets a git worktree. Commit your work; the orchestrator merges it.
- The task server runs at http://127.0.0.1:8052. Use it to report progress.
- Complete tasks by calling POST /tasks/{id}/complete with a result summary.
- If blocked, call POST /tasks/{id}/block with a reason.
- Do not modify files outside your assigned scope (check task owned_files).
- Run tests before marking done. The janitor will verify your work.
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.
- 3d ago First seen · 16 lines · 0 tokens per session scan A 5b8ea869db42
orchestration is a cursor rule published in the GitHub repository sipyourdrink-ltd/bernstein (1,038 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 173 tokens. 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
cursorrules
Do NOT invent repository facts. Before editing, run: npm run knowledge:context -- --task=" " and read .ai/local/current-context.md.
langchain
LangChain: chains, agents, memory, tools.
mcp-server
MCP (Model Context Protocol) server architecture and implementation.
fern-docs-generation
The custom internal Fern documentation generator automatically creates MDX documentation for Airweave connectors by introspecting Python source code using AST (Abstract Syntax Tree) parsing.
finops-enablement-lead
Builds and runs the training, documentation, champions network, and internal communication that turns individual engineers and product managers into daily FinOps practitioners. Scales the FinOps culture past the central team.
showback-chargeback-architect
Designs the model that turns shared cloud costs into team-level P&L. Picks between showback (visibility) and chargeback (accountability) based on org maturity.