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/dominion525/jetdb/agents-mdgit clone --depth 1 https://github.com/dominion525/jetdbWrote 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/dominion525/jetdb/agents-md)<a href="https://agentmods.dev/instructions/dominion525/jetdb/agents-md"><img src="https://agentmods.dev/badge/instructions/dominion525/jetdb/agents-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.00703 | $0.00703 |
| Opus 5 | $0.00351 | $0.00351 |
| Sonnet 5 | $0.00141 | $0.00141 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
jetdb 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 3d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project Overview
jetdb is a pure Rust, read-only library and CLI for Microsoft Access databases (.mdb/.accdb). Supports Jet3 (Access 97) through ACE17 (Access 2019).
Build & Test Commands
cargo build # Build all crates
cargo test -p jetdb # Library tests only
cargo test -p jetdb-cli # CLI tests only (unit + integration)
cargo test -p jetdb-cli --test cli_vba # Single integration test file
cargo test -p jetdb -- vba::tests::vba_v2003 # Single test by name
Architecture
Two-crate workspace:
- jetdb (
crates/jetdb/) — Core library. Low-level page reading with RC4 decryption (file.rs→PageReader), format constants (format.rs), then higher-level modules that all take&mut PageReader: catalog, table definitions, data rows, queries, relationships, properties, VBA extraction, DDL generation. - jetdb-cli (
crates/jetdb-cli/) — CLI binary. Each subcommand lives in its own module (query.rs,vba.rs,export.rs,prop.rs) or inline inmain.rs(ver, tables, schema). All public APIs are re-exported fromlib.rs.
Data flow: PageReader → read_catalog → read_table_def → read_table_rows → Value enum.
CLI Subcommand Pattern
All subcommands follow the same structure (see query.rs as the canonical example):
- Clap
Args/Subcommandstructs for CLI definition cmd_xxx(args) -> ExitCode— entry point, prints errors to stderr withjetdb:prefixrun_xxx(args) -> Result<(), FileError>— actual logic
List commands output sorted alphabetically. When data is absent (no tables, no queries, no VBA), return empty output (success), not an error. Name-not-found on show commands returns a specific error (e.g., ModuleNotFound, QueryNotFound).
Testing
- Test data:
testdata/with real .mdb/.accdb files organized by version (V1997, V2000, V2003, V2007, V2010, V2019) - All test files use
skip_if_missing!macro to gracefully skip when test data is absent - CLI integration tests use
Command::new(env!("CARGO_BIN_EXE_jetdb"))to invoke the binary - Library tests are in-module
#[cfg(test)] mod tests
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.
- 3d ago First seen · 63 lines · 703 tokens per session scan A 465ff3345f62
jetdb AGENTS.md is an instructions file published in the GitHub repository dominion525/jetdb (11 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 703 tokens to every session, about $0.0035 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
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).
spec-kit AGENTS.md
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.
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.
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.
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).
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.