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/timescale/tigerfs/claude-mdgit clone --depth 1 https://github.com/timescale/tigerfsWrote 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/timescale/tigerfs/claude-md)<a href="https://agentmods.dev/instructions/timescale/tigerfs/claude-md"><img src="https://agentmods.dev/badge/instructions/timescale/tigerfs/claude-md.svg" alt="Measured on agentmods" 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 | $0.03227 | $0.03227 |
| Opus 5 | $0.01614 | $0.01614 |
| Sonnet 5 | $0.00645 | $0.00645 |
| Haiku 4.5 | $0.00323 | $0.00323 |
Grade A, and why
tigerfs 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 4d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code when working with this repository.
Project Overview
TigerFS is a FUSE-based filesystem that exposes PostgreSQL databases as mountable directories. Users interact with tables, rows, and columns using Unix tools (ls, cat, grep, rm) instead of SQL.
Primary Goal: Enable Claude Code to explore and manipulate database data using Read/Glob/Grep operations.
Full specification: See docs/spec.md for complete technical details including filesystem structure, data formats, SQL patterns, and error codes.
Development Commands
# Build
go build -o bin/tigerfs ./cmd/tigerfs
# Test
go test ./... # All tests
go test -race ./... # With race detection
go test -run TestName ./path # Specific test
# Synth app tests
go test ./internal/tigerfs/fs/synth/... # Unit (synth package)
go test -run "^TestSynth_" ./internal/tigerfs/fs/... ./test/integration/... # Unit (synth_ops) + integration
# Before committing (required)
go fmt ./... && go vet ./... && go test ./... && go mod tidy
Architecture
Code Style
This is primarily a Go codebase. Follow Go idioms: error handling with explicit returns, table-driven tests, and gofmt formatting.
Key Packages
| Package | Purpose |
|---|---|
cmd/tigerfs/ |
Entry point with signal handling |
internal/tigerfs/cmd/ |
Cobra commands (pure functional builders) |
internal/tigerfs/fs/ |
Shared filesystem logic (path parsing, operations, stat cache) |
internal/tigerfs/fuse/ |
Linux FUSE adapter |
internal/tigerfs/nfs/ |
macOS NFS adapter |
internal/tigerfs/db/ |
PostgreSQL client and queries |
internal/tigerfs/backend/ |
Cloud backend resolution (Tiger, Ghost, postgres://) |
internal/tigerfs/mount/ |
Mount registry for tracking active mounts |
internal/tigerfs/config/ |
Viper-based configuration |
internal/tigerfs/logging/ |
Zap structured logging |
internal/tigerfs/format/ |
Data serialization (TSV, CSV, JSON) |
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.
- 4d ago First seen · 264 lines · 3,227 tokens per session scan A 8bbba29800b2
tigerfs CLAUDE.md is an instructions file published in the GitHub repository timescale/tigerfs (693 stars, last pushed 1mo ago), licensed MIT. It adds 3,227 tokens to every session, about $0.0161 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
supabase copilot-instructions.md
Copilot instructions for supabase/supabase, covering copilot code review instructions, review policy — read this first, confidence threshold, what not to comment on and what to comment on (priority order).
prest copilot-instructions.md
Copilot instructions for prest/prest, covering copilot instructions for prest go backend, project scope, core engineering principles, solid principles for go and s — single responsibility.
MCP-PostgreSQL-Ops copilot-instructions.md
Instructions for call518/MCP-PostgreSQL-Ops, covering architecture overview, core components, key patterns, in functions.py and development workflows.
postgres-skills AGENTS.md
Instructions for neondatabase/postgres-skills, covering agents.md, repository overview, creating a new skill, directory structure and naming conventions.
pg_exporter AGENTS.md
Instructions for nbari/pg_exporter, covering agents.md, project shape, first steps, devpod workflow (preferred) and local commands.
counterpoise-ledger CLAUDE.md
Instructions for jeffjjohnston/counterpoise-ledger, covering claude.md, project overview, development commands, essential commands and testing.