agentic-journeys: Skill for Claude Code

.github/skills/data-access-abstraction/SKILL.md

data-access-abstraction is a skill for Claude Code, Codex from microsoft/agentic-journeys. It costs 73 tokens per session (6,368 once invoked), scanned A, a copy of data-access-abstraction, MIT.

Guidance for putting database access behind a common layer, so an app can use SQLite locally and Cosmos DB or PostgreSQL in the cloud without changing its main code.

In plain words
What is it for?
Use it when building APIs that move from local development to Azure, adding database providers, or migrating between databases. It covers Node.js and TypeScript, Python with FastAPI, and .NET.
Why use it?
It avoids rewriting routes and business logic when the database changes. It also makes it easier to develop locally and test without connecting to a cloud database.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

This is microsoft/agentic-journeys's own configuration. It tells Claude Code and Codex how to work on agentic-journeys 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 agentic-journeys configures →

About the project

microsoft/agentic-journeys is a collection of guided projects that shows how AI coding agents and skills can plan, build, and deploy applications on Azure. It is for developers building Azure applications and teams evaluating agent-assisted development workflows, including APIs, databases, frontends, and AI features. The catalogue entries supply skills, agents, and instructions used in these journeys.

microsoft/agentic-journeys · 6 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to microsoft/agentic-journeys. 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/microsoft/agentic-journeys/main/.github/skills/data-access-abstraction/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/microsoft/agentic-journeys

Made for: Claude Code, Codex.

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-abstraction

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/agentic-journeys/data-access-abstraction/github.svg)](https://agentmods.dev/skills/microsoft/agentic-journeys/data-access-abstraction)
Your own site
<a href="https://agentmods.dev/skills/microsoft/agentic-journeys/data-access-abstraction"><img src="https://agentmods.dev/badge/skills/microsoft/agentic-journeys/data-access-abstraction/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-abstraction

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/agentic-journeys/data-access-abstraction"><img src="https://agentmods.dev/badge/skills/microsoft/agentic-journeys/data-access-abstraction.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,368 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 100% copy Near-identical to another mod 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.00073 $0.06368
Opus 5.5 $0.00029 $0.02547
Sonnet 5.5 $0.00015 $0.01274
Haiku 4.5 $0.00007 $0.00637

Measured 2mo ago against content hash 416a4fa1299c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

data-access-abstraction 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 2mo 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.

Origin

This is a copy

100% identical to data-access-abstraction — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/skills/data-access-abstraction/SKILL.md · 799 lines

How it starts

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

Data Access Abstraction

Build APIs with swappable data layers using the repository pattern. Develop locally with SQLite, deploy to Azure with Cosmos DB or PostgreSQL — same route code, different backend. Works in any language.

When to Use This Skill

  • Building an API that needs to run locally (SQLite) and in Azure (Cosmos DB or PostgreSQL)
  • Adding a new data provider to an existing app without changing routes or business logic
  • Migrating from one database to another incrementally
  • Any project following the AIMarket journey pattern (local dev → cloud deploy)

Pattern Overview

The pattern is the same regardless of language:

Routes/Controllers → Repository Interfaces → Factory → Implementations
                                                │
                                                ├── SQLite (local dev)
                                                ├── Cosmos DB (Azure deploy)
                                                ├── PostgreSQL (Azure deploy)
                                                └── In-memory (testing)

Three rules:

  1. Define repository interfaces (or abstract classes / protocols) per entity
  2. Routes depend only on the interfaces — never import a database client directly
  3. A factory reads a config value (DATA_PROVIDER) and returns the right implementation

Adding a new database means writing a new implementation file. Zero changes to routes.

Environment Variable

All languages use the same convention:

DATA_PROVIDER=sqlite     # Local development (default)
DATA_PROVIDER=cosmos     # Azure Cosmos DB
DATA_PROVIDER=postgres   # Azure PostgreSQL

Node.js / TypeScript

Repository Interfaces

// data/interfaces.ts

export interface IProductRepository {
  getAll(params: {
    page: number; pageSize: number;
    category?: string; minPrice?: number; maxPrice?: number;
  }): Promise<{ data: Product[]; totalCount: number }>;

  getById(id: string): Promise<Product | null>;
  create(input: CreateProductInput): Promise<Product>;
  update(id: string, fields: Partial<Product>): Promise<Product | null>;
}

export interface IOrderRepository {
  create(input: CreateOrderInput): Promise<Order>;
  getById(id: string): Promise<Order | null>;
  getByUserId(userId: string, page: number, pageSize: number): Promise<{ data: Order[]; totalCount: number }>;
}

export interface IUserRepository {
  create(input: CreateUserInput): Promise<User>;
  getById(id: string): Promise<User | null>;
  getByEmail(email: string): Promise<User | null>;
}

export interface DataStore {
  products: IProductRepository;
  orders: IOrderRepository;
  users: IUserRepository;
  close?(): void;
}

Read the full file on GitHub · 799 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. 2mo ago First seen · 799 lines · 73 tokens per session scan A 416a4fa1299c

Subscribe to this mod's changes

data-access-abstraction is a skill published in the GitHub repository microsoft/agentic-journeys (6 stars, last pushed 12d ago), licensed MIT. It adds 73 tokens to every session and 6,368 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to data-access-abstraction, differing in 0 lines, and is treated as a copy.

Related

data-access-abstraction compared with skills from other repositories

data-access-abstraction next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
data-access-abstractionmicrosoft/agentic-journeysSkill612d agoMITA73Claude Code, Codex
event-store-designwshobson/agentsSkill42kyesterdayMITA33Claude Code
platform-custom-field-generateforcedotcom/sf-skillsSkill1.1k2d agoApache-2.0A139Claude Code
field-service-sobject-create-configureforcedotcom/sf-skillsSkill1.1k2d agoApache-2.0A74Claude Code
durable-objectsfcakyon/claude-codex-settingsSkill1.2kyesterdayApache-2.0A22Claude Code
nornicdb-grpcorneryd/NornicDBSkill923yesterdayMITA98Claude Code, Codex
nw-ddd-eventsourcingnWave-ai/nWaveSkill631yesterdayMITA38Claude Code