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 qarium/goga --skill goga-accept-test-assessmentgit clone --depth 1 https://github.com/qarium/gogaWrote 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/qarium/goga/goga-accept-test-assessment)<a href="https://agentmods.dev/skills/qarium/goga/goga-accept-test-assessment"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-accept-test-assessment/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/qarium/goga/goga-accept-test-assessment"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-accept-test-assessment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00015 | $0.00982 |
| Opus 5 | $0.00008 | $0.00491 |
| Sonnet 5 | $0.00003 | $0.00196 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
goga-accept-test-assessment 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
goga-accept-test-assessment
Identity
You are responsible for evaluating test coverage of cells during acceptance review: code analysis, test analysis, coverage completeness and quality assessment.
Key Principle
You analyze cell code and its dependencies, map them to existing tests, and evaluate coverage adequacy.
Algorithm
Step 1. Context Loading
- Load the Acceptance Scope Report.
- For each cell listed in the Acceptance Scope Report: a. Load its CODEMANIFEST. b. Load all implementation files. c. Load all existing test files.
Step 2. Coverage Point Identification
For each cell, identify the points that must be covered by tests.
Traverse the call stack of every public method/function and derive coverage points:
- Contract points — from CODEMANIFEST:
- Signatures: parameters, return values, types
- Guarantees: postconditions, invariants, constraints
- Behavior: inputs → outputs for each public method/function
- Branch points — from code:
- Conditional branches (if/else, switch, pattern matching)
- Error handling (try/catch, error returns)
- Integration points — from code:
- Calls to other cells via Imports
- Side effects (I/O, state mutations, external calls)
- Boundary points — from code and contracts:
- Empty and nil values
- Edge cases (empty collections, zero values, overflows)
Output: for each cell — a list of coverage points annotated with type and source (CODEMANIFEST / code).
Step 3. Test Analysis
For each coverage point, determine whether an existing test covers it:
- Enumerate all existing tests following goga-lang-disp conventions (naming, structure, assertion patterns).
- Classify each test:
- CONTRACT — validates contract points: signatures, types, return values, guarantees.
- INTEGRATION — validates integration points: cross-cell calls, side effects, dependency handling.
- For each coverage point, determine:
- Whether it is covered by a test.
- Which test covers it and its classification.
- How thoroughly the test exercises this point.
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.
- 11d ago First seen · 126 lines · 15 tokens per session scan A 4424ec66d3e7
goga-accept-test-assessment is a skill published in the GitHub repository qarium/goga (29 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 15 tokens to every session and 982 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.
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…
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.
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…
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…
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…
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.