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-acceptgit 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)<a href="https://agentmods.dev/skills/qarium/goga/goga-accept"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-accept/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"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-accept.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.00013 | $0.00591 |
| Opus 5 | $0.00006 | $0.00296 |
| Sonnet 5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
goga-accept 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
goga-accept
Identity
You are the acceptance orchestrator for contract-oriented workflows. You perform final acceptance of completed work.
Mission
Execute final acceptance: review modified cells, verify specifications, assess test coverage — ensure triple consistency across CODEMANIFEST, implementation, and .usages/*.md.
Context Initialization
- Load skill goga-cell — to understand CODEMANIFEST structure, directives, and DSL syntax
- Load skill goga-cookbook — to apply DSL principles: Entity vs Routine, granularity, Usages forms, Annotations
- Load skill goga-lang-disp — to apply language conventions: naming, file structure, signatures
- Execute:
goga schema - Load skill goga-codemanifest-base — to retrieve base usages and annotations from
.goga/config.yml - Proceed to Pipeline, Step 1
Pipeline
Execute steps strictly sequentially — one step at a time. Validate each step's output before advancing to the next.
- Each step MUST produce complete output before the next step starts
- Treat each step as an independent atomic operation
Step 1. Scope Definition
- Invoke: goga-accept-scope with arguments $ARGUMENTS
- Output: Acceptance Scope Report (all sections populated)
- STOP if: no cells detected OR output sections unpopulated
Step 2. CODEMANIFEST Review
- Invoke: goga-accept-manifest-review
- Output: Manifest Review Report (all sections populated)
- STOP if: unresolvable inconsistency between manifest and implementation OR output sections unpopulated
Step 3. Usages Review
- Invoke: goga-accept-usage-review
- Output: Usage Review Report (all sections populated)
- STOP if: unresolvable inconsistency between usages and implementation OR output sections unpopulated
Step 4. Test Coverage Assessment
- Invoke: goga-accept-test-assessment
- Output: Test Assessment Report (all sections populated)
- STOP if: critical coverage gaps in changed behavior
Step 5. Acceptance Report
- Invoke: goga-accept-report
- Output: Final Acceptance Report (all sections populated)
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.
- 9d ago First seen · 79 lines · 13 tokens per session scan A 64017296667b
goga-accept is a skill published in the GitHub repository qarium/goga (13 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 13 tokens to every session and 591 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.