bash-gres CLAUDE.md

Instructions for bash-gres, a tool that gives AI agents a virtual file system stored in PostgreSQL, a database system. It explains the main design and supported database connectors.

In plain words
What is it for?
Use it when setting up bash-gres, connecting it through Drizzle, node-postgres, or postgres.js, or integrating it with just-bash.
Why use it?
It helps agents work with bash-gres without guessing how its file system, database access, and connector layers fit together.

Instructions file

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 instructions/marcoripa96/bash-gres/claude-md
Clone the repo
git clone --depth 1 https://github.com/marcoripa96/bash-gres
Per session 1,899 This file is loaded in full into every session.
When invoked 1,899 The same file — it is already loaded in full.
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.01899 $0.01899
Opus 5 $0.00949 $0.00949
Sonnet 5 $0.00380 $0.00380
Haiku 4.5 $0.00190 $0.00190

Measured 2d ago against content hash 989bf8554a48, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bash-gres CLAUDE.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 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.

CLAUDE.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

bash-gres

PostgreSQL-backed virtual filesystem for AI agents. PgFileSystem implements the just-bash IFileSystem interface, so it can be passed directly to new Bash({ fs }).

Architecture

bash-gres (core)          PgFileSystem, setup(), search, types
bash-gres/drizzle         Drizzle adapter (createDrizzleClient) + schema
bash-gres/node-postgres   node-postgres (pg) adapter (createNodePgClient)
bash-gres/postgres        postgres.js adapter (createPostgresClient)

Core + Adapter pattern

The core operates on a SqlClient interface (query(text, params) + transaction(fn)). Adapters wrap driver-specific connections into SqlClient:

  • postgres.js: createPostgresClient(sql) from bash-gres/postgres
  • node-postgres (pg): createNodePgClient(pool) from bash-gres/node-postgres
  • Drizzle: createDrizzleClient(db) from bash-gres/drizzle

Then pass the resulting SqlClient to PgFileSystem({ db: client }) and setup(client). Core has zero knowledge of any specific driver.

The Drizzle adapter (lib/adapters/drizzle/adapter.ts) converts $1, $2 positional params into Drizzle's sql tagged template.

Bash integration

PgFileSystem structurally implements the just-bash IFileSystem interface. Users pass it directly:

import { Bash } from "just-bash";
const bash = new Bash({ fs: pgFs });
await bash.exec("echo hello > /file.txt");

Key modules

  • lib/core/types.ts: SqlClient, FsError, SqlError, all option/result interfaces
  • lib/core/filesystem.ts: PgFileSystem class with all fs operations (implements IFileSystem)
  • lib/core/filesystem/ops/: per-op implementations installed onto PgFileSystem.prototype (one file per op, e.g. list-history.ts, version-diff.ts, merge.ts); shared SQL helpers live next to them (fetch-diff.ts, fetch-page-changes.ts, fetch-version-changes.ts)
  • lib/core/setup.ts: idempotent DDL: extensions, table, indexes, RLS, optional pgvector
  • lib/core/path-encoding.ts: path <-> ltree conversion using _xHEX_ delimited encoding
  • lib/core/search.ts: BM25 full-text search via pg_textsearch, optional pgvector semantic/hybrid
  • lib/core/mounts.ts: mount allow-list (default-deny scoping to subtrees of one workspace). Sibling to exclude.ts: compileMounts + mountVisible/mountWritable (JS guards) + mountWhereSql (the path <@ ANY OR path @> ANY clause threaded into every listing/walk/glob/search query via buildMountClause)
  • lib/adapters/drizzle/adapter.ts: converts Drizzle db into SqlClient (DrizzleDb interface, createDrizzleClient)
  • lib/adapters/drizzle/schema.ts: Drizzle pgTable with all indexes (GiST, BM25, partial)
  • lib/adapters/node-postgres/index.ts: wraps pg.Pool into SqlClient (structural NodePgPool interface)
  • lib/adapters/postgres/index.ts: wraps postgres.Sql into SqlClient

Read the full file on GitHub · 108 lines

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. 2d ago First seen · 108 lines · 1,899 tokens per session scan A 989bf8554a48

Subscribe to this mod's changes

bash-gres CLAUDE.md is an instructions file published in the GitHub repository marcoripa96/bash-gres (21 stars, last pushed 19d ago), licensed MIT. It adds 1,899 tokens to every session, about $0.0095 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.

Related

Other instructions, from other repositories

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.

openai/codex · 5,182 tokens

buildNext

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

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

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

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,040 tokens

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

langchain-ai/langchain · 4,345 tokens