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-contextgit 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-context)<a href="https://agentmods.dev/skills/qarium/goga/goga-brainstorm-context"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-brainstorm-context/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-context"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-brainstorm-context.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.00014 | $0.00700 |
| Opus 5 | $0.00007 | $0.00350 |
| Sonnet 5 | $0.00003 | $0.00140 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
goga-brainstorm-context 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
goga-brainstorm-context
Identity
You are responsible for gathering facts about the current state of the project.
Context
Use this report for its specific purpose:
[INTAKE_REPORT]— use it for the topic, the user's description, and any names/terms it mentions; these drive the matching against the project schema (Read relevant CODEMANIFESTs) and the choice of usages to read (Read relevant usages).
Workflow
Phase 1. Get the project schema
Run goga schema --help first to understand the command's capabilities, then run goga schema to obtain the complete cell hierarchy. To understand what a cell is, use skill goga-cell.
If the project has no existing architecture — record this as a fact and proceed.
Phase 2. Record base usages and annotations
Use skill goga-codemanifest-base — record base usages and annotations for all CODEMANIFESTs in the plan.
Phase 3. Read relevant CODEMANIFESTs
Based on the schema and the [INTAKE_REPORT], read the CODEMANIFESTs of cells possibly related to the topic. Match the user's description to the schema:
- Names matching cell paths or types may be existing artifacts — verify by reading CODEMANIFEST, present as hypothesis
- Names without matches may be new artifacts to create
- If the description has no specific names — identify affected cells by meaning
- If names are ambiguous (multiple matches) — flag for hypothesis-based clarification
- Use
--depends-on <cell_path>to search dependent cells when necessary
Phase 4. Read relevant usages
Read usages of files related to the cells from Phase 3, following the rules of skill goga-cookbook.
If the task implies external libraries or technologies — read usages about them in .goga/usages/cooks/.
This provides a catalog of available practices, libraries, and tools that the new architecture can reference.
Adapt depth:
- Related to the topic → read fully
- Indirectly related → read annotations and key sections
- No existing CODEMANIFESTs → skip
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 · 83 lines · 14 tokens per session scan A 40cf1ccb97c2
goga-brainstorm-context is a skill published in the GitHub repository qarium/goga (25 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 14 tokens to every session and 700 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"…
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…
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…
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…