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 instructions/sipyourdrink-ltd/bernstein/copilot-instructionsgit 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.00740 | $0.00740 |
| Opus 5 | $0.00370 | $0.00370 |
| Sonnet 5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
bernstein copilot-instructions.md 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions
Bernstein is a deterministic orchestrator for CLI coding agents (Python 3.12+), one git worktree per task. There is no model in the coordination loop - the orchestrator is deterministic Python, NOT an LLM - so the same plan replays to a byte-identical task graph.
Architecture
src/bernstein/
core/ # 21 sub-packages (orchestration, agents, tasks, quality, ...)
__init__.py # MetaPathFinder redirects old imports to sub-packages
defaults.py # All configurable constants (150+)
server.py # FastAPI task server (HTTP :8052)
orchestration/ # Run loop, ticks, drain, scheduling
agents/ # Lifecycle, spawning, identity, signals
tasks/ # Lifecycle, store, claim, retry, models
quality/ # Gates, testing, review, architecture
security/ # Auth, RBAC, permissions, compliance
observability/ # Metrics, tracing, logging, alerting
protocols/ # MCP, A2A, ACP, gRPC, cluster
routing/ # Model routing, policies, bandit
cost/ # Tracking, budgets, forecasting
tokens/ # Monitoring, context, compaction
config/ # Seed parsing, settings, feature gates
git/ # Operations, worktrees, merge
persistence/ # Store backends, WAL, checkpoints
planning/ # Plans, recipes, planner
communication/ # Bulletin, notifications, signals
knowledge/ # Knowledge base, RAG, memory
plugins_core/ # Plugin management, skills
adapters/ # CLI agent adapters (claude, codex, gemini, etc.)
cli/ # CLI commands (commands/, display/, utils/, plan/)
tui/ # Textual TUI widgets
Key constraints
- The orchestrator/scheduler is deterministic Python. NEVER add LLM calls for coordination.
- Agents are short-lived: spawn per task, execute, exit. No long-running sessions.
- All runtime state lives in
.sdd/as files (JSONL, YAML). No databases. - Use frozen dataclasses/TypedDict for all data - never raw dicts.
- Type hints on ALL public functions. Pyright strict mode must pass.
- Async for IO-bound, sync for CPU-bound.
- New constants go in
core/defaults.py, not inline. - New modules go in the appropriate sub-package, not in
core/root.
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.
- yesterday First seen · 70 lines · 740 tokens per session scan A 9c9ee5123513
bernstein copilot-instructions.md is an instructions file published in the GitHub repository sipyourdrink-ltd/bernstein (1,038 stars, last pushed today), licensed Apache-2.0. It adds 740 tokens to every session, about $0.0037 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 instructions, from other repositories
agent-orchestrator AGENTS.md
AGENTS.md instructions for Untrivial-ai/agent-orchestrator, covering agents.md, repo layout, commands, where to look first and distribution.
agent-orchestrator CLAUDE.md
Claude Code instructions for Untrivial-ai/agent-orchestrator, covering claude.md, app state lives under /.ao only and design system.
yoloai CLAUDE.md
Instructions for kstenerud/yoloai, covering claude code specifics and the quality gate runs itself here.
jentic-one GEMINI.md
Instructions for jentic/jentic-one: Otherwise, read AGENTS.md — this repo's canonical agent guidance.
contextweaver routing.instructions.md
Instructions for dgenio/contextweaver, covering routing engine — agent instructions, choicegraph validation invariants (graph.py), treebuilder grouping strategies (tree.py), router beam-search constraints (router.py) and catalog invariants (catalog.py).
technocore-chat AGENTS.md
AGENTS.md instructions for flop-labs-dev/technocore-chat: CI runs exactly these — run them before pushing.