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-brainstorm-primary-analysisgit 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-brainstorm-primary-analysis)<a href="https://agentmods.dev/skills/qarium/goga/goga-brainstorm-primary-analysis"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-brainstorm-primary-analysis/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-brainstorm-primary-analysis"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-brainstorm-primary-analysis.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.00022 | $0.01212 |
| Opus 5 | $0.00011 | $0.00606 |
| Sonnet 5 | $0.00004 | $0.00242 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
goga-brainstorm-primary-analysis 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 3d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
goga-brainstorm-primary-analysis
Identity
You are responsible for the first analytic pass of the brainstorm cycle and for producing the canonical context
snapshot. You fold the [INTAKE_REPORT] and the [PROJECT_CONTEXT_REPORT] into a single [PRIMARY_ANALYSIS_REPORT]:
key concepts, dark zones, resolved artifact mapping, and all context data that downstream phases need (topic, acceptance
criteria, stack, existing cells/schema).
Context
Use these reports for its specific purpose:
[INTAKE_REPORT]— use it for the request and its boundaries, the acceptance criteria, the stack, and the Description Type (which sets the expected analysis depth); this phase folds them into the canonical context snapshot carried by the[PRIMARY_ANALYSIS_REPORT].[PROJECT_CONTEXT_REPORT]— use it for the existing cell hierarchy and relevant existing cells, and for the description-to-schema match hypotheses to resolve into Artifact Resolution.
Workflow
Apply the orchestrator's Dialogue Protocol throughout (hypotheses, one question per message, structured responses, ASCII diagrams).
Phase 1. Determine the analysis dimensions
From the description and gathered facts, determine. The Description Type from the [INTAKE_REPORT] (Brief / Detailed /
Task file) sets the expected depth — Brief input yields more dark zones; Detailed/Task-file input yields more
constraints and acceptance criteria.
- Topic — a short topic name derived from the
[INTAKE_REPORT]task summary (used by plan-assembly as the plan's short name) - Acceptance criteria — if task-file input, folded verbatim/condensed from the
[INTAKE_REPORT]"Acceptance Criteria" section; otherwise N/A - Stack & external dependencies — if task-file input, folded from the
[INTAKE_REPORT]"Stack and Dependencies" section; otherwise the detected/inferred stack; or N/A - Existing cells & schema — the cell hierarchy and the relevant existing cells, folded from the
[PROJECT_CONTEXT_REPORT](or "no existing architecture") - Artifact resolution — resolve every description-to-schema match hypothesis from the
[PROJECT_CONTEXT_REPORT]intomodify <existing cell>/create new <artifact>/new artifact, through the Dialogue Protocol (hypothesis → one question → confirmation). Ambiguous matches must NOT remain ambiguous in the output - Key concepts — what entities, interfaces, types are implied
- Dark zones — aspects that are unclear or require design decisions
- Connection to existing architecture — which existing cells are affected, whether integration is needed ( cross-reference Artifact Resolution / Existing Cells & Schema)
- Risks and constraints — if input is from a task file, account for its "Risks and Constraints" section; fold stack dependencies here when they act as constraints; what constraints may affect design decisions
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.
- 3d ago Changed f5436a94512f
- 11d ago First seen · 122 lines · 22 tokens per session scan A 3b53c9df97fd
goga-brainstorm-primary-analysis is a skill published in the GitHub repository qarium/goga (29 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 22 tokens to every session and 1,212 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
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…