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-define-challengegit 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-define-challenge)<a href="https://agentmods.dev/skills/qarium/goga/goga-define-challenge"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-define-challenge/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-define-challenge"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-define-challenge.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.00006 | $0.01793 |
| Opus 5 | $0.00003 | $0.00897 |
| Sonnet 5 | $0.00001 | $0.00359 |
| Haiku 4.5 | $0.00001 | $0.00179 |
Grade A, and why
goga-define-challenge 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 10d 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 — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
goga-define-challenge
Purpose
Challenge the complete product definition before the PRD is generated.
Review the entire product context as one coherent system and identify contradictions, missing decisions, logical gaps, unsupported assumptions, and product behaviours that remain insufficiently defined.
The challenge is a validation stage, not another product-design stage.
Contract
consume:
- product
- problem
- users
- goals
- user_experience
- requirements
- constraints
- scope
- success_criteria
produce:
- conflicts
Core Principle
Do not ask whether the PRD sounds reasonable.
Ask whether the product decision is internally consistent and sufficiently complete to be handed to engineering for technical design.
The challenge must actively try to break the current product definition.
Look for contradictions across the entire context, not only within the most recently produced section.
Product Interview
The challenge stage must distinguish between:
- a contradiction that can be resolved from the established context;
- a product decision that requires the user's choice.
If the context contains enough information to resolve a contradiction, resolve it through the normal resolver flow.
If two or more materially different product interpretations remain valid and the context does not establish which one is intended, report the decision as requiring user input.
Do not choose an interpretation merely because it appears more reasonable.
Validation Model
Review the following relationships:
Product
↓
Problem
↓
Users
↓
Goals
↓
User Experience
↓
Requirements
↓
Constraints
↓
Scope
↓
Success Criteria
Every stage should support the next one.
The complete model must also remain consistent in the reverse direction:
Success Criteria
↓
Goals
↓
Problem
Process
1. Validate the problem
Check:
- Is the problem clearly defined?
- Is it a real product problem rather than a feature request?
- Is it specific enough to guide the solution?
- Does the proposed product change actually address it?
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.
- 10d ago First seen · 445 lines · 6 tokens per session scan A c33aa218c94a
goga-define-challenge is a skill published in the GitHub repository qarium/goga (25 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 6 tokens to every session and 1,793 once invoked, about $0.0000 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
doubt-driven-review
In-flight adversarial check on a non-trivial decision BEFORE it stands — distinct from post-hoc review of a finished diff. Use on "stress-test this decision", "are we sure about this", "verify before commit", "poke holes in this", when working in unfamiliar code, or before an irreversible step (migration, prod deploy…
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
spec-coherence-check
Sweep all active OpenSpec proposals for staleness, conflicts, and obsolescence against the current codebase and archived changes. Use when proposals may be outdated, when checking cross-proposal conflicts, or before starting a batch of implementations. Produces a gap-analysis report, updates a priority queue file, and…
faq-mine
Mine docs/faq.md from README.md, docs/.md, and the pi-hermes memory stores. Dispatches @fast subagents per source, dedupes against the existing FAQ, and merges entries in caveman style. Use when asked to "build / regenerate / extend the FAQ", "mine docs into FAQ", "mine hermes memory into FAQ", "surface runtime…
session-to-guideline
Turn a pi session into a Markdown "how-we-did-it" collaboration guideline: reads the session's JSONL transcript and synthesizes a reusable playbook of which prompts worked, what had to be steered, and how to reproduce the result faster. Use when: "document this session", "write up how we did X with the AI", "make a…