goga-brainstorm-intake

goga-brainstorm-intake is a skill for Claude Code from qarium/goga. It costs 16 tokens per session (436 once invoked), scanned A, original, BSD-3-Clause.

An input-handling procedure for the brainstorm pipeline. It accepts an architecture request, identifies whether it is brief, detailed, or a task-file request, and extracts relevant requirements when a task file is supplied.

In plain words
What is it for?
Use it to read task files under `docs/tasks/`, capture current state, boundaries, technology choices, acceptance criteria, risks, and scope, then recommend how the work should be split.
Why use it?
It turns different kinds of requests into a consistent starting point for architecture work. It also flags when one request contains several independent subsystems that may need separate discussions.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to read task files under docs/tasks/, capture current state, boundaries, technology choices, acceptance criteria, risks, and scope, then recommend how the work should be split.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/qarium/goga/goga-brainstorm-intake
View source ↗ qarium/goga
Install

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.

Any agent
npx skills add qarium/goga --skill goga-brainstorm-intake
Clone the repo
git clone --depth 1 https://github.com/qarium/goga

Made for: Claude Code.

Wrote 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.

agentmods badge for goga-brainstorm-intake

README.md
[![agentmods](https://agentmods.dev/badge/skills/qarium/goga/goga-brainstorm-intake/github.svg)](https://agentmods.dev/skills/qarium/goga/goga-brainstorm-intake)
Your own site
<a href="https://agentmods.dev/skills/qarium/goga/goga-brainstorm-intake"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-brainstorm-intake/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.

agentmods 80×15 button for goga-brainstorm-intake

Your own site · 80×15
<a href="https://agentmods.dev/skills/qarium/goga/goga-brainstorm-intake"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-brainstorm-intake.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 436 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.00436
Opus 5 $0.00008 $0.00218
Sonnet 5 $0.00003 $0.00087
Haiku 4.5 $0.00002 $0.00044

Measured 3d ago against content hash 20e0d3d358a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

goga-brainstorm-intake 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.

goga/assets/skills/goga-brainstorm-intake/SKILL.md · 66 lines

What it actually says

goga-brainstorm-intake

Identity

You are responsible for accepting and normalizing the user's architecture request.

Workflow

Phase 1. Receive the description

Receive the user's description of what needs to be designed (the orchestrator's $ARGUMENTS). Retain the original description verbatim for the entire session.

Phase 2. Classify the description

Classify the description into one of:

  • Brief — one sentence or a feature name
  • Detailed — a complete specification with requirements, constraints, examples
  • Task file — a path to a task file (e.g., the path printed by goga history path -f task.md)

Phase 3. Read the task file if provided

If a task file is given — read it and extract sections:

  • Current state → context for primary analysis
  • Description and Boundaries → basis for design
  • Stack and External Dependencies → account for when choosing technologies
  • Acceptance Criteria → condition for final approval
  • Risks and Constraints → account for during primary analysis
  • Scope → if split into subtasks, flag for one-subtask-at-a-time brainstorm

Phase 4. Check scope

If the description covers several independent subsystems — record a split recommendation (which subsystem to brainstorm first).

Output Format

Fill every section. No empty sections.

# [INTAKE_REPORT]

## Task Summary
[One paragraph: what was requested]

## Description Type
[Brief / Detailed / Task file]

## Task-File Sections
[Only if a task file was provided: Current state, Description and Boundaries, Stack and Dependencies, Acceptance Criteria, Risks and Constraints, Scope. Otherwise: N/A]

## Original Description
[The user's description, verbatim]

## Scope Split Decision
[Single subsystem → proceed; multiple subsystems → recommendation to split and which one to brainstorm first]

STOP if:

  • description is empty
  • multiple independent subsystems detected and the split is unresolved
Changes

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.

  1. 3d ago Changed 20e0d3d358a8
  2. 11d ago First seen · 66 lines · 16 tokens per session scan A 27377f441e86

Subscribe to this mod's changes

goga-brainstorm-intake is a skill published in the GitHub repository qarium/goga (29 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 16 tokens to every session and 436 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.

Related

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…

BlackBeltTechnology/pi-agent-dashboard · 90 tokens

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"…

BlackBeltTechnology/pi-agent-dashboard · 93 tokens

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…

BlackBeltTechnology/pi-agent-dashboard · 80 tokens

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…

BlackBeltTechnology/pi-agent-dashboard · 92 tokens

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…

BlackBeltTechnology/pi-agent-dashboard · 94 tokens

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…

BlackBeltTechnology/pi-agent-dashboard · 93 tokens