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-contracts-usages-inlinegit 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-contracts-usages-inline)<a href="https://agentmods.dev/skills/qarium/goga/goga-brainstorm-contracts-usages-inline"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-brainstorm-contracts-usages-inline/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-contracts-usages-inline"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-brainstorm-contracts-usages-inline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00024 | $0.00533 |
| Opus 5 | $0.00012 | $0.00267 |
| Sonnet 5 | $0.00005 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
goga-brainstorm-contracts-usages-inline 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 11d 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.
What it actually says
goga-brainstorm-contracts-usages-inline
Algorithm
Connect every practice the cell consumes into its CODEMANIFEST header.
- Syntax and semantics of the
UsagesandImports.Usagesdirectives (keys, paths, aliasing, conflict rules) followgoga-cell. - The choice of connection form (file / URL / inline) and when a practice is worth declaring follow
goga-cookbook.
Step 1 — Collect what the cell consumes
Build the factual basis for all three categories from the reports:
- From
[CELL_DISTRIBUTION_REPORT]— the types this cell imports from other cells (inter-cellImports). - From
[TYPE_DETAIL_REPORT]— each type's responsibility, signatures, and interactions; identify the external libraries, patterns, and formats the types rely on.
Step 2 — Base usages
Take all base usages from goga-codemanifest-base as-is and add them to the Usages directive unchanged.
Where a base practice constrains the contract form (error style, naming, pattern), the contract must comply — flag it
so the annotations step enforces it.
Step 3 — Cross-cell usages
For every type imported from another cell (Step 1): if the provider cell has .usages/ files describing how to work
with that type's API, connect them via Imports.Usages. Resolve any name clash with a local Usages key through the
AS alias (goga-cell). These document the provider's facade — they do not impose obligations on this contract.
Step 4 — External usages
For every external library, pattern, or format the cell relies on (Step 1): look for an existing usage file in
.goga/usages/ or .goga/usages/cooks/. If found, connect it via Usages in the form goga-cookbook
prescribes for the situation. If none exists, record it in External Usage Gaps.
Return
Return the connected base / cross-cell / external usages and the set of Usages keys (the backtick targets the annotations step references).
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.
- 11d ago First seen · 47 lines · 24 tokens per session scan A 4d8dc37b839a
goga-brainstorm-contracts-usages-inline is a skill published in the GitHub repository qarium/goga (29 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 24 tokens to every session and 533 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…