agentmods.dev

goga-accept-scope

goga-accept-scope is a skill for Claude Code, Codex from qarium/goga. It costs 20 tokens per session (528 once invoked), scanned A, original, BSD-3-Clause.

A guide for deciding which parts of a codebase need acceptance testing for a particular feature. It maps that feature, or the files changed in Git, to the relevant project cells and checks their required files.

In plain words
What is it for?
Use it to identify the acceptance-test scope from a feature description or Git changes, inspect the project schema, and verify each matched cell's manifest and usage files.
Why use it?
It prevents testing either too little or unrelated parts of the project when the affected functionality is unclear.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: names the AskUserQuestion tool.

not rated 13repo 2d ago A scan SkillSpector: pass 20 tokens original BSD-3-Clause

Good fit Use it to identify the acceptance-test scope from a feature description or Git changes, inspect the project schema, and verify each matched cell's manifest and usage files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/qarium/goga/goga-accept-scope
View source ↗ qarium/goga
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 qarium/goga --skill goga-accept-scope
Clone the repo
git clone --depth 1 https://github.com/qarium/goga

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 goga-accept-scope

README.md
[![agentmods](https://agentmods.dev/badge/skills/qarium/goga/goga-accept-scope/github.svg)](https://agentmods.dev/skills/qarium/goga/goga-accept-scope)
Your own site
<a href="https://agentmods.dev/skills/qarium/goga/goga-accept-scope"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-accept-scope/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 goga-accept-scope

Your own site · 80×15
<a href="https://agentmods.dev/skills/qarium/goga/goga-accept-scope"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-accept-scope.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 528 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.00020 $0.00528
Opus 5 $0.00010 $0.00264
Sonnet 5 $0.00004 $0.00106
Haiku 4.5 $0.00002 $0.00053

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

Security

Grade A, and why

goga-accept-scope 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 9d 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.

goga/assets/skills/goga-accept-scope/SKILL.md · 72 lines

How it starts

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

goga-accept-scope

Identity

You are responsible for defining the acceptance scope — identifying the set of cells associated with a given functionality.

Algorithm

Determine acceptance scope

Acceptance operates at the functionality level. One functionality may span one or more cells.

Resolve the scope:

  1. Arguments contain a functionality description or path — use as <target>
  2. Arguments are empty — analyze git diff to identify changed files
  3. No changes found or scope is ambiguous — prompt the user via AskUserQuestion:
    • question: "Which functionality should undergo acceptance?"
    • header: "Acceptance scope"
    • multiSelect: false
    • options:
      • label: "Branch changes", description: "Determine from git diff"
      • label: "Specific functionality", description: "Provide a functionality description"
      • label: "All project cells", description: "Full acceptance"

Map scope to cells

  1. Load the project schema: goga schema
  2. Match the functionality description or git diff results to cells in the schema
  3. For each matched cell: a. Verify the CODEMANIFEST file exists b. Load the CODEMANIFEST c. Verify the .usages/ directory exists d. Classify change types: CODE / MANIFEST / USAGE / TEST
  4. Discover dependent cells — cells that import the matched cells
  5. Classify each dependency:
    • DIRECT — imports a changed API
    • TRANSITIVE — imports a DIRECT dependency
  6. Generate the Acceptance Scope Report

STOP if:

  • No cells are discovered
  • A cell lacks a CODEMANIFEST
  • The scope is ambiguous

Output format

Complete every section. Empty sections are not allowed.

# Acceptance Scope Report

## Data source
[How the scope was resolved: arguments, git diff, or user selection]

## Functionality
[Functionality description, if determined]

## Cells for acceptance
[Table: Cell | Path | Change types (CODE/MANIFEST/USAGE/TEST)]

## Affected dependencies
[Table: Dependent cell | Dependency type (DIRECT/TRANSITIVE) | Impact assessment]

## Scope summary
[Total cells, total files, distribution by change categories]

Read the full file on GitHub · 72 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. 9d ago First seen · 72 lines · 20 tokens per session scan A 09f14a6915f3

Subscribe to this mod's changes

goga-accept-scope is a skill published in the GitHub repository qarium/goga (13 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 20 tokens to every session and 528 once invoked, about $0.0001 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.

Testingagent-frameworkagent-orchestrationagent-skillsagenticagentic-aiagentic-workflow
Related

Other skills, from other repositories

scenario-design

Draft real-life test SCENARIOS (not smoke tests) from a change/feature spec. Derives edge-case, performance, frontend-quirk and error-handling scenarios with ISTQB techniques, routes each to a test level, and writes test-plan.md, emitting clarification questions on a spec gap. Use on "design test scenarios", "what…

BlackBeltTechnology/pi-agent-dashboard · 88 tokens

run-dashboard-e2e-local-changes

Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.

BlackBeltTechnology/pi-agent-dashboard · 42 tokens

rn-testing

This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…

Lykhoyda/rn-dev-agent · 106 tokens

capturing-proof

This skill should be used when the user asks to "capture proof", "record a demo of this feature", "make a video showing it works", "record the flow for the PR", "generate a PR body", "capture screenshots for the PR", "proof-capture", or when a verified feature needs PR-ready proof artifacts (video + numbered…

Lykhoyda/rn-dev-agent · 105 tokens

run-action

Explicit Codex workflow: Execute a learned Maestro flow ("action") by name with optional -e KEY=VALUE parameters. Looks the flow up via packages/rn-dev-agent-core/dist/learned-actions.js (same inventory as $rn-dev-agent:list-learned-actions), then replays it via cdprunaction — auto-repair-aware orchestration with…

Lykhoyda/rn-dev-agent · 99 tokens

build-and-test

Explicit Codex workflow: Build the Expo/React Native app (local or EAS), install it, start Metro, then test a requested feature end-to-end.

Lykhoyda/rn-dev-agent · 37 tokens