directory-context

A set of per-directory context files that tell coding agents what a folder is for, which files matter, what rules must hold, and how to test changes there.

In plain words
What is it for?
Use it to document rules for source folders and test suites, guide agents through repository subtrees, and record the correct tests for each area.
Why use it?
It gives agents the local project knowledge they need when different parts of a codebase have different conventions and checks.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/sipyourdrink-ltd/bernstein/directory-context
Clone the repo
git clone --depth 1 https://github.com/sipyourdrink-ltd/bernstein

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 232 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00232
Opus 5 $0.00000 $0.00116
Sonnet 5 $0.00000 $0.00046
Haiku 4.5 $0.00000 $0.00023

Measured yesterday against content hash 93b433473326, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

directory-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 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.

.cursor/rules/directory-context.mdc · 20 lines

What it actually says

Per-directory context files for agents working inside a subtree. Each covers: what the directory is for, key files, invariants, and how to test that subtree.

Path Covers
src/bernstein/adapters/AGENTS.md CLI agent adapters
src/bernstein/cli/AGENTS.md Click CLI
src/bernstein/core/lineage/AGENTS.md Lineage: artifact provenance
src/bernstein/core/orchestration/AGENTS.md Orchestration engine
src/bernstein/core/quality/AGENTS.md Quality gates and verification
src/bernstein/core/security/AGENTS.md Security: audit chain, identity, policy
tests/AGENTS.md Test suite
Changes

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.

  1. yesterday First seen · 20 lines · 0 tokens per session scan A 93b433473326

Subscribe to this mod's changes

directory-context is a cursor rule published in the GitHub repository sipyourdrink-ltd/bernstein (1,038 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 232 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.