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-design-by-changesgit 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-design-by-changes)<a href="https://agentmods.dev/skills/qarium/goga/goga-design-by-changes"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-design-by-changes/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-design-by-changes"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-design-by-changes.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.00017 | $0.03523 |
| Opus 5 | $0.00009 | $0.01761 |
| Sonnet 5 | $0.00003 | $0.00705 |
| Haiku 4.5 | $0.00002 | $0.00352 |
Grade A, and why
goga-design-by-changes 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.
How it starts
The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design by Changes
Purpose
The agent produces a design document — a complete architectural specification derived from CODEMANIFEST changes.
The design document specifies what to implement and how to implement it.
The agent does not write implementation code. The agent does not produce an execution plan. The agent produces an architectural specification where every detail is fully elaborated.
Phase 1: DSL Loading
Step 1: Load the DSL specification
The agent invokes goga-cell via the Skill tool.
Use goga-cell for:
- Understanding cell structure (CODEMANIFEST,
.usages/) - Interpreting directives (Imports, Usages, Annotations, types, mutations, embeddings)
- Validating syntactic correctness
Step 2: Load the DSL application principles
The agent invokes goga-cookbook via the Skill tool.
Use goga-cookbook for:
- Selecting between Entity and Routine
- Determining cell granularity
- Choosing the Usages connection form (file / inline / URL)
- Applying principles for writing usage files in
.usages/
Phase 2: Change Collection
Step 1: Git diff CODEMANIFEST
The agent diffs all CODEMANIFEST files between the current branch and the base branch.
Identify:
- Added, removed, and modified contract entities
- Changes to Usages, Imports, Annotations, and re-exports
- New or deleted CODEMANIFEST files
Output: Change list grouped by CODEMANIFEST file with entity-level detail.
Step 2: Schema — dependency map
The agent executes goga schema to retrieve the cell hierarchy.
Apply --depends-on <cell_path> for each path from Step 1 to locate affected cells.
Output: Dependency map scoped to affected cells.
Phase 3: Contract Validation
The phase objective: produce a clean CODEMANIFEST before deep tracing begins. Resolve all static contract defects at this stage.
Step 1: Resolve Usages references
Determine which Usages entries require reading:
- Gather changed entities — from Phase 2
- Always read root Usages — referenced by global
Annotations - Always read Usages of changed entities — referenced by entity/method/property annotations
- Skip unreferenced Usages — where no changed entity and no global annotation references them
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed · -1 lines 65b6c6a689dd
- 7d ago First seen · 336 lines · 17 tokens per session scan A 4ac564f68c57
goga-design-by-changes is a skill published in the GitHub repository qarium/goga (29 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 17 tokens to every session and 3,523 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-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…