ynab-sqlite-export AGENTS.md

A set of coding instructions for a small Python tool that exports a YNAB budget into a SQLite database. YNAB is a budgeting application, and SQLite is a local database stored in a file.

In plain words
What is it for?
Use it when changing the exporter or querying its database. It explains the dependency-free design, incremental synchronisation, schema changes, required filters, and protection of tokens and personal database files.
Why use it?
It prevents analyses from treating deleted records as active data or counting transfers as income and spending, which would produce misleading totals.

Instructions file for CodexOpenCode

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/rubick/ynab-sqlite-export/agents-md
Clone the repo
git clone --depth 1 https://github.com/RuBiCK/ynab-sqlite-export

Made for: Codex, OpenCode.

Per session 293 This file is loaded in full into every session.
When invoked 293 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.00293 $0.00293
Opus 5 $0.00147 $0.00147
Sonnet 5 $0.00059 $0.00059
Haiku 4.5 $0.00029 $0.00029

Measured yesterday against content hash d0e2163ade1f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ynab-sqlite-export 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 yesterday.

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.

AGENTS.md · 24 lines

What it actually says

Agent guide

This repo is a single-file tool: ynab_to_sqlite.py dumps a YNAB account into ynab.db (SQLite). Stdlib-only Python 3, no build step, no tests to run beyond executing the script itself.

Working on the tool

  • Keep it dependency-free and generic: no hardcoded budget IDs, category names, currencies, or personal assumptions — anyone's YNAB token must work.
  • Incremental sync relies on YNAB's server_knowledge delta cursors stored in the sync_state table. If you change the schema, bump users via --full (which drops and recreates all tables) and say so in the README.
  • Never commit .env or *.db (both gitignored) — they contain the maintainer's real token and real financial data.

Querying a ynab.db produced by this tool

Full guidance (schema, pitfalls, ready-made SQL) lives in .claude/skills/ynab-db/SKILL.md — read it before writing SQL. The two mistakes that silently corrupt every analysis: forgetting deleted = 0 (deletes are soft) and counting transfers (transfer_account_id IS NOT NULL) as income/spending.

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. yesterday First seen · 24 lines · 293 tokens per session scan A d0e2163ade1f

Subscribe to this mod's changes

ynab-sqlite-export AGENTS.md is an instructions file published in the GitHub repository RuBiCK/ynab-sqlite-export (10 stars, last pushed 1mo ago), licensed MIT. It adds 293 tokens to every session, about $0.0015 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-31.

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