project-context

project-context is a skill for Claude Code from upex-galaxy/agentic-qa-boilerplate. It costs 85 tokens per session (969 once invoked), scanned A, original, MIT.

A workflow for creating or refreshing maps of a project's business data, features, APIs, and master test plan. These maps describe the project's entities, user-facing functions, API behavior, and prioritized testing work.

In plain words
What is it for?
Use it to build or update business maps, document API and feature coverage, create a master test plan, or refresh all four context documents in a defined order.
Why use it?
It gives QA and development work a shared view of what the product contains and what matters most to test. It also prevents a broad refresh request from silently changing several planning areas at once.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md; installed under .agents/ (shared by several agents); mentions AGENTS.md.

Good fit Use it to build or update business maps, document API and feature coverage, create a master test plan, or refresh all four context documents in a defined order.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/upex-galaxy/agentic-qa-boilerplate/project-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 project-context
Clone the repo
git clone --depth 1 https://github.com/upex-galaxy/agentic-qa-boilerplate

Made for: Claude Code.

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 project-context

README.md
[![agentmods](https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/project-context.svg)](https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/project-context)
Your own site
<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/project-context"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/project-context.svg" alt="Measured on agentmods" height="20"></a>
Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 969 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00085 $0.00969
Opus 5 $0.00043 $0.00485
Sonnet 5 $0.00017 $0.00194
Haiku 4.5 $0.00009 $0.00097

Measured 8d ago against content hash 18dd47088d72, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

project-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 8d 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/project-context/SKILL.md · 60 lines

How it starts

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

Project Context

Own the four regenerative project-context artifacts without duplicating their workflows across harness commands.

Compact Rules

  • Exactly ONE mode per run: data · features · api · test-plan · refresh-all. Load only that mode's reference; never open a second one in the same pass.
  • Mode → reference → output: datareferences/data.md.context/business/business-data-map.md · featuresreferences/features.md.context/business/business-feature-map.md · apireferences/api.md.context/business/business-api-map.md · test-planreferences/test-plan.md.context/master-test-plan.md.
  • User did not name a mode → ASK. NEVER infer refresh-all from a generic "refresh the context" request.
  • refresh-all runs strictly datafeaturesapitest-plan, one at a time. Each reference's own validation and approval gate must close before the next is loaded. Never skip ahead.
  • Artifact missing = CREATE mode: may write once the analysis completes. Artifact exists = UPDATE mode: generate a candidate, show the diff summary, WAIT for explicit approval. NEVER overwrite an existing artifact without that approval.
  • Stop the run on a hard dependency failure or a rejected overwrite. A missing SOFT dependency is not a stop: record it as a Discovery Gap and continue, exactly as the selected reference defines.
  • NEVER invent business facts. Read every source the selected reference requires; anything unverified belongs under the output's mandatory ## Discovery Gaps section, not asserted in the body.
  • After a successful artifact write, add the pointer to AGENTS.md ONLY when that pointer is missing. Never add operational prose to CLAUDE.md.
  • Forward $ARGUMENTS unchanged to the selected mode.

Read full SKILL.md when: the requested mode is ambiguous, a refresh-all chain fails mid-sequence, or you need the selected reference's own analysis steps and validation gate.

Mode routing

Resolve one mode from the invocation. Load only the reference named in that row.

Read the full file on GitHub · 60 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. 8d ago First seen · 60 lines · 85 tokens per session scan A 18dd47088d72

Subscribe to this mod's changes

project-context is a skill published in the GitHub repository upex-galaxy/agentic-qa-boilerplate (21 stars, last pushed 3d ago), licensed MIT. It adds 85 tokens to every session and 969 once invoked, about $0.0004 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-30.