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.
npx skills add upex-galaxy/agentic-qa-boilerplate --skill business-api-contextgit clone --depth 1 https://github.com/upex-galaxy/agentic-qa-boilerplateWrote 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.
[](https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/business-api-context)<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/business-api-context"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/business-api-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.
<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/business-api-context"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/business-api-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00163 | $0.01130 |
| Opus 5.5 | $0.00065 | $0.00452 |
| Sonnet 5.5 | $0.00033 | $0.00226 |
| Haiku 4.5 | $0.00016 | $0.00113 |
Grade A, and why
business-api-context scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| the running API of the active environment (`curl`, `agentic-qa-core/references/api-testing-doctrine.md`) | real statuses and bodies | wins for behaviour | 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-api-context
Kind
contextwith 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-api-context(or--section <id>for one endpoint group). NEVER readreferences/business-api-map.htmlraw: 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-contextmodeapi; never answer API questions as if the API were empty. - DO: take field names, types and required flags from the schema (
[API_TOOL]schema read,api/schemas/), and the MEANING from the map. On a conflict the schema wins for shape, the running API wins for behaviour. - WHEN a session observes something that contradicts a section (a status, a field, an auth rule): 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, noapi/schemas/, no product code. - DO NOT: copy map content into this SKILL.md. Judgment goes in
## Rulesorreferences/gotchas.md, dated and measured. - Before a step that uses
api-schema(verifying a section) ordiagrams(redrawing a figure), run the point-of-use check inagentic-qa-core/references/preflight-gate.md§8.
Read full SKILL.md when: building a briefing for an API-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 API as a business surface. Which endpoint groups exist and what each one is for, who is allowed to call them, what they change, how a multi-call flow chains them, what each error means to a user, and which third parties sit behind them. Loading it changes what the agent KNOWS; the only thing it ever does is propose an edit to its own map.
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.
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.
- 5d ago Changed 985562459b15
- 16d ago First seen · 61 lines · 163 tokens per session scan A 2d335b46019d
business-api-context is a skill published in the GitHub repository upex-galaxy/agentic-qa-boilerplate (26 stars, last pushed 4d ago), licensed MIT. It adds 163 tokens to every session and 1,130 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-01.
Other skills, from other repositories
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.
afrexai-api-architect
Design, build, test, document, and secure production-grade APIs. Covers the full lifecycle from schema design through deployment, monitoring, and versioning. Use when designing new APIs, reviewing existing ones, generating OpenAPI specs, building test suites, or debugging production issues.
verify
Build, launch, and drive the AppointMe stack to verify a change end-to-end at its runtime surface.
pdlc-api-mock
A command that reads API design documents and creates realistic sample responses and configuration for a mock service. A mock service imitates an API so frontend code can be tested before the real backend is ready.
test-integration
Test how components work together. Test database + API, auth + user service, etc. Use when testing multi-component flows or after unit tests pass.
backend
Backend development skill for microservices following Clean Architecture, CQRS with a transactional outbox, the repository/use-case pattern, and a Testing-Trophy strategy.