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-plan-assemblygit 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-plan-assembly)<a href="https://agentmods.dev/skills/qarium/goga/goga-brainstorm-plan-assembly"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-brainstorm-plan-assembly/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-plan-assembly"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-brainstorm-plan-assembly.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.00015 | $0.00722 |
| Opus 5 | $0.00008 | $0.00361 |
| Sonnet 5 | $0.00003 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
goga-brainstorm-plan-assembly 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 2d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
goga-brainstorm-plan-assembly
Identity
You are responsible for assembling the architecture plan — a structured document describing CODEMANIFEST and .usages/
files for each cell — and writing it to disk.
Context
Use these reports for its specific purpose:
[CELL_ASSEMBLY_REPORT]— use it for the assembled per-cell CODEMANIFESTs and.usages/files, the dependency diagram, and the artifact list — the material to write into the plan.[PRIMARY_ANALYSIS_REPORT]— use its Topic as the plan's short name, its Existing Cells & Schema for the project structure (file names and paths), and its Artifact Resolution to mark each cell as modified vs created anew.
Workflow
Phase 1. Determine the topic
Resolve the topic directory — the path printed by goga history path (the current topic in the history tree).
Keep the Topic section of the [PRIMARY_ANALYSIS_REPORT] as the plan's short name.
Phase 2. Assemble the plan structure
Build the plan with the following sections.
Implementation order
Cells ordered from leaves to root (cells without dependencies first, then dependent ones). For each cell, specify the reason for the order (e.g., "has no Imports", "depends on cell X").
Artifacts for each cell
For each cell in implementation order:
- CODEMANIFEST — complete file contents in DSL format
- .usages/ files — for each file: path, name, complete contents
Dependency map
ASCII diagram or list of connections between cells via Imports.
Verification checklist
What to check after implementing each artifact.
Phase 3. Apply plan generation rules
- Each CODEMANIFEST in the plan must be syntactically correct per the DSL specification
- File names and paths must correspond to the project structure from the Existing Cells & Schema section of the
[PRIMARY_ANALYSIS_REPORT] - For modification of existing CODEMANIFESTs — specify a diff: what to add, change, delete
- Explicitly mark which cells are modified vs created anew (per the Artifact Resolution in the
[PRIMARY_ANALYSIS_REPORT]) - The plan contains ONLY CODEMANIFEST and
.usages/file artifacts — no implementation code in any language
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.
- 2d ago Changed · +2 lines 9c9f9a08b03e
- 10d ago First seen · 96 lines · 15 tokens per session scan A 6d95bea266d0
goga-brainstorm-plan-assembly is a skill published in the GitHub repository qarium/goga (25 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 15 tokens to every session and 722 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…