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-define-projectgit 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-define-project)<a href="https://agentmods.dev/skills/qarium/goga/goga-define-project"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-define-project/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-define-project"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-define-project.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.00005 | $0.01569 |
| Opus 5 | $0.00003 | $0.00785 |
| Sonnet 5 | $0.00001 | $0.00314 |
| Haiku 4.5 | $0.00001 | $0.00157 |
Grade A, and why
goga-define-project 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 7d 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
goga-define-project
Purpose
Understand the current project before defining a product change that must fit into an existing product.
Use the project's structural context to understand:
- what the existing product contains;
- which cells are relevant to the requested change;
- how those cells relate to the product;
- what existing capabilities may already solve part of the problem;
- where the requested change naturally belongs.
This skill provides product context for an existing project. It does not design the change.
Contract
consume:
- input
produce:
- product
Core Principle
Understand the existing product before proposing changes to it.
The requested change must be evaluated against what already exists.
Do not assume that the requested capability is missing simply because the user asks for it.
Do not redesign the existing product.
The goal is to provide enough context for subsequent skills to reason about the change without rediscovering the project structure themselves.
Product Decisions
This skill is responsible for understanding the existing product, not deciding what the new product change should be.
Use the project context to answer factual questions about the current product yourself.
Do not infer the user's desired change when multiple reasonable interpretations exist.
If the existing product context reveals multiple materially different ways the requested change could fit into the product, ask the user which direction is intended.
The user should decide product intent. The project should provide product facts.
Source of Truth
Use:
goga schema
# for understand json use
goga schema --help
as the primary source for understanding the current project structure.
The schema describes the project's cells and provides their descriptions.
When the meaning, structure, or purpose of a cell is unclear, use the goga-cell skill to understand the cell model and its conventions.
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.
- 7d ago First seen · 345 lines · 5 tokens per session scan A 2dabd295f098
goga-define-project is a skill published in the GitHub repository qarium/goga (29 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 5 tokens to every session and 1,569 once invoked, about $0.0000 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-09-03.
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…