business-data-context

business-data-context is a skill for Claude Code, Codex from upex-galaxy/agentic-qa-boilerplate. It costs 154 tokens per session (1,077 once invoked), scanned A, original, MIT.

A project-specific map of the system’s business data: its entities, relationships, states, automatic processes, integrations, and data flows.

In plain words
What is it for?
Use it when investigating databases, data validation, triggers, scheduled jobs, webhooks, or flows that move data between systems.
Why use it?
It prevents an agent from guessing what database records mean or how they change. It also identifies stale or missing information before data-related answers are given.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions Codex; mentions OpenCode.

Good fit Use it when investigating databases, data validation, triggers, scheduled jobs, webhooks, or flows that move data between systems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/upex-galaxy/agentic-qa-boilerplate/business-data-context
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.

Any agent
npx skills add upex-galaxy/agentic-qa-boilerplate --skill business-data-context
Clone the repo
git clone --depth 1 https://github.com/upex-galaxy/agentic-qa-boilerplate

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 business-data-context

README.md
[![agentmods](https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/business-data-context/github.svg)](https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/business-data-context)
Your own site
<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/business-data-context"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/business-data-context/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 business-data-context

Your own site · 80×15
<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/business-data-context"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/business-data-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 154 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,077 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.00154 $0.01077
Opus 5.5 $0.00062 $0.00431
Sonnet 5.5 $0.00031 $0.00215
Haiku 4.5 $0.00015 $0.00108

Measured 16d ago against content hash f1e704ec17af, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

business-data-context 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 16d 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/business-data-context/SKILL.md · 61 lines

How it starts

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

business-data-context

Kind context with a declared write scope (agentic-qa-core/references/skill-composition-strategy.md §2b). Delivered once by upstream as a placeholder, then owned by the project: the map inside is this project's synthesis. Procedure: agentic-qa-core/references/business-context-maps.md.

Compact Rules

  • DO: read the map through bun run context:map business-data-context (or --section <id> for one entity or flow). NEVER read references/business-data-map.html raw: its SVG is most of the bytes and none of the facts.
  • DO: treat a placeholder map as "no map". Say so and hand the user project-context mode data; never answer data questions as if the system were empty.
  • DO: cite a fact with its section id and data-updated date. A section older than the code it describes is a hypothesis to check with [DB_TOOL], not an answer.
  • WHEN a session observes something that contradicts a section: PROPOSE the one-section edit with its evidence to the user (or to the conductor when you are a supervised worker), apply it only on approval. Procedure: references/refresh.md.
  • DO NOT: write anywhere but this skill's own references/. No Jira, no .context/, no other skill, no product code.
  • DO NOT: copy map content into this SKILL.md. Judgment (a rule for READING the data) goes in ## Rules or references/gotchas.md, dated and measured.
  • Before a step that uses db (verifying a section) or diagrams (redrawing a figure), run the point-of-use check in agentic-qa-core/references/preflight-gate.md §8.

Read full SKILL.md when: building a briefing for a DB-level dispatch, deciding whether a section is stale, or proposing an edit to the map.

What this skill knows

One aspect of the system under test: its data. Which business entities exist and why, how they relate, which states each one moves through and what fires the transitions, what runs automatically, which external services read or write it, and the end-to-end flows (User -> API -> Logic -> DB -> Response) that move it. Loading it changes what the agent KNOWS; the only thing it ever does is propose an edit to its own map.

Read the full file on GitHub · 61 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 16d ago First seen · 61 lines · 154 tokens per session scan A f1e704ec17af

Subscribe to this mod's changes

business-data-context is a skill published in the GitHub repository upex-galaxy/agentic-qa-boilerplate (26 stars, last pushed 4d ago), licensed MIT. It adds 154 tokens to every session and 1,077 once invoked, about $0.0006 per session on Opus 5.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-10-01.

Related

Other skills, from other repositories

pytest-databases

Auto-activate for pytestdatabases, Docker DB fixtures, PostgreSQL/pgvector/ParadeDB, MySQL/MariaDB, Oracle/SQL Server, CockroachDB, MongoDB, Redis/Valkey, BigQuery/Spanner, MinIO, or RustFS. Not for mocked DBs.

litestar-org/litestar-skills · 69 tokens

database-testing

Validate database integrity, test migrations forward and backward, verify schema constraints, manage seed data, detect migration drift, and identify query performance issues. Covers PostgreSQL, MySQL, MongoDB with Prisma, TypeORM, Drizzle, and SQLAlchemy, plus Testcontainers test databases. Use when: "database test,"…

petrkindlmann/qa-skills · 158 tokens

test-data-management

Create and manage test data with factory patterns, fixture strategies, data anonymization, and synthetic data generation. Covers Fishery (TypeScript), FactoryBot (Ruby), Factory Boy (Python), database seeding, cleanup strategies, and GDPR-compliant data handling. Use when: "test data," "fixtures," "factories," "seed…

petrkindlmann/qa-skills · 132 tokens

agent-testing-harness

Use this skill when testing AI agent systems. Activate when the user needs to test agent behavior, write tests for multi-agent systems, implement agent evaluation frameworks, create test harnesses for autonomous agents, or validate agent outputs systematically.

latestaiagents/agent-skills · 51 tokens

api-test-patterns

Write comprehensive API tests for REST and GraphQL endpoints. Use this skill when testing APIs, writing contract tests, or validating integrations. Activate when: api testing, REST test, GraphQL test, endpoint testing, integration test, postman, contract testing.

latestaiagents/agent-skills · 56 tokens

graphrag-patterns

Implement GraphRAG patterns combining knowledge graphs with retrieval for complex reasoning. Use this skill when building RAG over interconnected data or needing relationship-aware retrieval. Activate when: GraphRAG, knowledge graph, graph retrieval, entity relationships, Neo4j RAG, graph database, connected data.

latestaiagents/agent-skills · 65 tokens