business-e2e-context

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

A project-specific map of how people use the system from start to finish. It records user types, journeys, branches, failure points, and the features those journeys cross.

In plain words
What is it for?
Use it to plan or review end-to-end and user-interface tests, especially flows involving several features, payments, or hand-offs between steps.
Why use it?
It prevents end-to-end tests from focusing only on isolated screens or features while missing the real user flow and important data changes.

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 to plan or review end-to-end and user-interface tests, especially flows involving several features, payments, or hand-offs between steps.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/business-e2e-context"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/business-e2e-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 169 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,115 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.00169 $0.01115
Opus 5.5 $0.00068 $0.00446
Sonnet 5.5 $0.00034 $0.00223
Haiku 4.5 $0.00017 $0.00112

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

Security

Grade A, and why

business-e2e-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-e2e-context/SKILL.md · 62 lines

How it starts

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

business-e2e-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-e2e-context (or --section <id> for one journey or feature). NEVER read references/business-e2e-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 e2e; never plan E2E coverage as if the product had no journeys.
  • DO: start from the journey, then the feature. A story is tested inside the journey that reaches it; the feature catalog answers "what exists", the journeys answer "what a user does and where it breaks".
  • WHEN a session observes something that contradicts a section (a step, a branch, a state the UI shows): 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 test code, no product code.
  • DO NOT: copy map content into this SKILL.md. Judgment goes in ## Rules or references/gotchas.md, dated and measured.
  • Before a step that uses 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 UI or E2E dispatch, scoping a smoke or regression run, 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 use, end to end. Who the users are, which journeys they take and where each one can fail, which features exist and which journeys cross them, and the flows that only make sense across several features. 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 · 62 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 · 62 lines · 169 tokens per session scan A d1ae39fc30e7

Subscribe to this mod's changes

business-e2e-context is a skill published in the GitHub repository upex-galaxy/agentic-qa-boilerplate (26 stars, last pushed 4d ago), licensed MIT. It adds 169 tokens to every session and 1,115 once invoked, about $0.0007 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.