Borrowing it
Nothing to install: this file belongs to BetterThanTomorrow/calva-backseat-driver. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/BetterThanTomorrow/calva-backseat-driver/master/.github/instructions/backseat-driver-source-conventions.instructions.mdgit clone --depth 1 https://github.com/BetterThanTomorrow/calva-backseat-driverWrote 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/instructions/betterthantomorrow/calva-backseat-driver/backseat-driver-source-conventions)<a href="https://agentmods.dev/instructions/betterthantomorrow/calva-backseat-driver/backseat-driver-source-conventions"><img src="https://agentmods.dev/badge/instructions/betterthantomorrow/calva-backseat-driver/backseat-driver-source-conventions/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/instructions/betterthantomorrow/calva-backseat-driver/backseat-driver-source-conventions"><img src="https://agentmods.dev/badge/instructions/betterthantomorrow/calva-backseat-driver/backseat-driver-source-conventions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.01225 | $0.01225 |
| Opus 5 | $0.00613 | $0.00613 |
| Sonnet 5 | $0.00245 | $0.00245 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
calva-backseat-driver backseat-driver-source-conventions.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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backseat Driver Source Conventions
Naming Conventions
function!— side effectsfunction+— returns promisefunction!+— side effects and promisefunction?— predicate!atom-name— atom (e.g.,!app-db,!output-conn)ax.prefix — pure action handlerfx.prefix — impure effect handlerex/namespace — framework plumbing, not domain logic
Ex Framework Patterns
Actions (axs.cljs)
Actions are pure functions. They receive immutable state and arguments, return a map of changes:
{:ex/db new-state ;; state update (merged at end)
:ex/dxs [[:ns/ax.name ...]] ;; deferred actions (dispatched after state update)
:ex/fxs [[:ns/fx.name ...]]} ;; effect declarations (executed after dxs)
Actions never access atoms, VS Code APIs, or external state directly. Use enrichment placeholders:
:context/some.path— resolved from VS Code extension context[:db/get :key]— resolved from current app-db state:vscode/config.settingName— resolved from VS Code configuration
Effects (fxs.cljs)
Effects are impure handlers that receive dispatch!, context, and the enriched effect vector. They perform side effects and may dispatch new actions:
(defn some-effect! [dispatch! context [_ args]]
(-> (some-async-operation!+ args)
(.then (fn [result]
(dispatch! context [[:ns/ax.handle-result result]])))))
Async Continuation
Effects return promises. Continuation actions use :ex/then, :ex/on-success, :ex/on-error with placeholder enrichment:
;; In action — declare effect with continuation
{:ex/fxs [[:ns/fx.do-thing {:data data
:ex/then [[:ns/ax.thing-done :ex/action-args]]}]]}
;; In effect — enrich continuation and dispatch
(.then promise
(fn [result]
(dispatch! context (ax/enrich-with-args then-actions result))))
Routing
Actions route by (namespace action-keyword): "app", "mcp", "db", "vscode", "node", "calva".
Effects route similarly. Add new routes in ex/ax.cljs (handle-action) and ex/fx.cljs (perform-effect!).
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.
- 9d ago First seen · 113 lines · 1,225 tokens per session scan A 2bec2e490deb
calva-backseat-driver backseat-driver-source-conventions.instructions.md is an instructions file published in the GitHub repository BetterThanTomorrow/calva-backseat-driver (64 stars, last pushed 11d ago), licensed MIT. It adds 1,225 tokens to every session, about $0.0061 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.