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/tigrisdata/objgit/agents-mdgit clone --depth 1 https://github.com/tigrisdata/objgitWhat 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.01405 | $0.01405 |
| Opus 5 | $0.00702 | $0.00702 |
| Sonnet 5 | $0.00281 | $0.00281 |
| Haiku 4.5 | $0.00140 | $0.00140 |
Grade A, and why
objgit AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository guidelines
objgitd is a single-binary git server. It stores repositories as objects in
a Tigris bucket, and not on a local filesystem.
Module path: tangled.org/xeiaso.net/objgit. Go 1.26.
Transports
One backend answers three transports:
| Transport | Flag | Default | Notes |
|---|---|---|---|
| Smart HTTP | -http-bind |
:8080 |
The primary transport. Carries HTTP Basic. |
| git:// | -git-bind |
:9418 |
Unauthenticated TCP. Opt-in. |
| SSH | -ssh-bind |
off | Public-key. Opt-in. Host key lives in the bucket. |
All three funnel authorization through one pluggable
internal/auth.Authorizer.
A fourth listener serves Prometheus metrics at /metrics (-metrics-bind,
default :9090). An empty value disables it.
Commands
go build ./... # build everything
go build -o objgitd ./cmd/objgitd
go test ./... # full test suite
go test ./cmd/objgitd/... # protocol tests
go test -run TestSmartHTTP ./cmd/objgitd/...
go test -run TestSSH ./cmd/objgitd/...
# Run locally.
./objgitd -bucket $BUCKET -http-bind :8080 -allow-push
./objgitd -bucket $BUCKET -ssh-bind :2222 -allow-push # git clone ssh://git@host:2222/repo.git
Notes on the tests and on configuration:
- Protocol tests need
giton PATH. They skip themselves without it. - SSH tests also need
sshandssh-keygenon PATH. They skip themselves without them. - Flags can also come from the environment through
flagenv, which maps each flag to UPPER_SNAKE.-allow-pushbecomesALLOW_PUSH, and-bucketbecomesBUCKET. godotenvloads a.envfile from the working directory at startup.- Tigris client credentials come from the standard AWS SDK chain, such as
AWS_PROFILE.
Where the code lives
| Path | Purpose |
|---|---|
cmd/objgitd/main.go |
Builds the one *daemon and starts every listener. |
cmd/objgitd/git_protocol.go |
The git:// server. Also holds operationFor and (*daemon).authorize. |
cmd/objgitd/http.go |
Smart HTTP. *daemon is the http.Handler itself. |
cmd/objgitd/ssh.go |
The SSH server and its per-session dispatch. |
cmd/objgitd/receivepack.go |
The go-git fork that streams hook output, plus writePack. |
cmd/objgitd/hooks.go |
Ref diffing and the sandboxed hook run. |
internal/auth |
The one authorization interface. |
internal/repofs |
Maps a repository path to a storage.Storer. |
internal/storage/tigris |
Repository storage. A storage.Storer on the bucket. |
internal/bundler |
The async upload queue behind that storer. |
internal/s3fs |
Daemon-level state only, which is the SSH host key. |
internal/mountfs, internal/treefs, internal/kefkash |
The hook sandbox filesystem and shell wiring. |
internal/metrics |
Every Prometheus vector, plus thin helpers. |
internal/slog.go |
JSON handler init. |
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.
- 2d ago First seen · 114 lines · 1,405 tokens per session scan A d1204414e5aa
objgit AGENTS.md is an instructions file published in the GitHub repository tigrisdata/objgit (53 stars, last pushed 4d ago), licensed MIT. It adds 1,405 tokens to every session, about $0.0070 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
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.
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).
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.
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).
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.
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.