mcp-server-for-ynab: Skill for Claude Code

.agents/skills/data-access-discipline/SKILL.md

data-access-discipline is a skill for Claude Code from hs737/mcp-server-for-ynab. It costs 21 tokens per session (585 once invoked), scanned A, original, Apache-2.0.

A set of coding rules for keeping database access clear and separate from web transport and business rules. It covers schemas, queries, migrations, persistence helpers, and tenant or scope boundaries.

In plain words
What is it for?
Use it when changing database tables or queries, adding migrations or repositories, reviewing data-access structure, or enforcing which tenant can access records.
Why use it?
It helps prevent database logic from being scattered through request handlers or mixed with unrelated application policy.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is hs737/mcp-server-for-ynab's own configuration. It tells Claude Code how to work on mcp-server-for-ynab itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-server-for-ynab configures →

Part of the mcp-server-for-ynab plugin — 12 skills, 2 MCP servers shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to hs737/mcp-server-for-ynab. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/hs737/mcp-server-for-ynab/master/.agents/skills/data-access-discipline/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/hs737/mcp-server-for-ynab

Made for: Claude Code.

Or install mcp-server-for-ynab, the plugin that ships this one along with the rest of its 12 skills, 2 MCP servers.

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

agentmods badge for data-access-discipline

README.md
[![agentmods](https://agentmods.dev/badge/skills/hs737/mcp-server-for-ynab/data-access-discipline/github.svg)](https://agentmods.dev/skills/hs737/mcp-server-for-ynab/data-access-discipline)
Your own site
<a href="https://agentmods.dev/skills/hs737/mcp-server-for-ynab/data-access-discipline"><img src="https://agentmods.dev/badge/skills/hs737/mcp-server-for-ynab/data-access-discipline/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for data-access-discipline

Your own site · 80×15
<a href="https://agentmods.dev/skills/hs737/mcp-server-for-ynab/data-access-discipline"><img src="https://agentmods.dev/badge/skills/hs737/mcp-server-for-ynab/data-access-discipline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 585 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00021 $0.00585
Opus 5 $0.00010 $0.00293
Sonnet 5 $0.00004 $0.00117
Haiku 4.5 $0.00002 $0.00059

Measured 9d ago against content hash 431513bee6d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

data-access-discipline 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 9d 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.

.agents/skills/data-access-discipline/SKILL.md · 59 lines

How it starts

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

Data Access Discipline

Use this skill when adding tables, queries, migrations, persistence helpers, cross-entity writes, or scope or tenant enforcement.

Use When

  • Adding or changing schema
  • Writing new queries
  • Adding persistence helpers or repository modules
  • Adding cross-table workflows
  • Reviewing DB access placement
  • Tightening scope or tenant rules

Read First

  • AGENTS.md (if present)
  • README.md
  • Architecture and data docs in this repo (for example docs/architecture.md, docs/data-access-patterns.md, docs/data-model.md, docs/environment.md)
  • Migration tooling config (for example alembic.ini, SQLAlchemy models under src/, Django migrations—whatever this repo uses)

Core Rules

  1. Persistence code should be consistent and discoverable.
  2. Business rules should not be buried in route or MCP tool handlers.
  3. Persistence helpers should not quietly own domain policy.
  4. Cross-entity workflows should have a clear orchestration layer (service/module), not ad hoc scripts.
  5. Scope or tenant boundaries should be enforced explicitly.
  6. Schema changes, migrations, and related docs should move together.
  7. Domain-facing shapes should be intentional, not accidental spillover from ORM rows or raw dicts.
  8. Single source of truth: Prefer normalized tables and explicit columns for durable state. In-memory aggregates assembled for reads must not be duplicated as parallel persisted blobs unless documented and intentional.
  9. Multi-write consistency: When several SQL statements must succeed or fail together, use one outer transaction (session.begin(), async with session.begin(), or equivalent). Pass the same session/connection into helpers; avoid nested transaction calls that commit independently. Keep slow network or external API calls outside the transaction; persist only after durable inputs are ready.

Workflow

  1. Identify whether the task is schema, query, migration, or workflow related.
  2. Place query or persistence logic in the repo’s established pattern.
  3. Keep cross-entity business logic out of thin repository functions.
  4. Review whether scope and ownership enforcement are explicit.
  5. Update migrations, docs, and tests as needed.

Read the full file on GitHub · 59 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. 9d ago First seen · 59 lines · 21 tokens per session scan A 431513bee6d1

Subscribe to this mod's changes

data-access-discipline is a skill published in the GitHub repository hs737/mcp-server-for-ynab (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 585 once invoked, about $0.0001 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 skills, from other repositories

api-canvas

DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…

cyanheads/obsidian-mcp-server · 85 tokens

api-mirror

Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.

cyanheads/obsidian-mcp-server · 68 tokens

webmcp-nexus

A coding guide for adding WebMCP tools to JavaScript or TypeScript projects. WebMCP lets AI agents call selected application functions through a standard interface.

alibaba/webmcp-nexus · 159 tokens

cmdb-patterns

Create ServiceNow CIs and cmdbrelci relationships, walk upstream/downstream impact, detect orphan/stale CIs, and align discovered CIs with the proper sysclassname hierarchy.

serac-labs/serac · 43 tokens

gliderecord-patterns

Write efficient ServiceNow GlideRecord queries — addQuery vs addEncodedQuery, setLimit, GlideAggregate for counts, avoiding N+1 in loops, query operators, and safe CRUD with workflow control.

serac-labs/serac · 46 tokens

organize-database

Transform unstructured Notion pages into a well-designed database with proper schema and migration.

n24q02m/better-notion-mcp · 21 tokens