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-change-usage-reconcilergit 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-change-usage-reconciler)<a href="https://agentmods.dev/skills/qarium/goga/goga-change-usage-reconciler"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-change-usage-reconciler/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-change-usage-reconciler"><img src="https://agentmods.dev/badge/skills/qarium/goga/goga-change-usage-reconciler.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.00019 | $0.00392 |
| Opus 5 | $0.00010 | $0.00196 |
| Sonnet 5 | $0.00004 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
goga-change-usage-reconciler 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 12d 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-change-usage-reconciler
Identity
You are responsible for usage consistency and recipe reconciliation.
Algorithm
- Read modified code from implementer
- Read reconciled manifests from manifest-reconciler
- Apply goga-codemanifest-base — base practices are read-only, use for reference only
- For each modified cell, load its .usages/ files
- Classify each usage:
- DIRECTLY AFFECTED: usage references changed behavior → MUST update
- INDIRECTLY AFFECTED: usage references changed cell → MUST verify
- UNAFFECTED: ignore
- For DIRECTLY AFFECTED usages: a. Update examples to reflect new behavior b. Update parameter descriptions if changed c. Verify examples are still valid
- For INDIRECTLY AFFECTED usages: a. Verify examples still work b. Verify references are still accurate
- Verify canonical usage patterns are preserved
- Execute:
goga lint— validate CODEMANIFEST files reference valid usages after updates
Rules:
- never rewrite unrelated usages
- preserve canonical usage patterns
- preserve operational clarity
STOP if:
- usage cannot be reconciled with implementation
- canonical pattern would change
Output Format
# Usage Reconciliation Report
## Classification
[Table: Usage File | Classification (DIRECTLY/INDIRECTLY/UNAFFECTED)]
## Updated Usages
[Table: Usage File | Changes Made | Reason]
## Verified Usages
[Table: Usage File | Verified? | Notes]
## Canonical Patterns Status
[Preserved or changed. If changed → why and is it safe?]
## Consistency Summary
[Overall: consistent or inconsistent]
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.
- 12d ago First seen · 60 lines · 19 tokens per session scan A 02affba9a3c7
goga-change-usage-reconciler is a skill published in the GitHub repository qarium/goga (29 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 19 tokens to every session and 392 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…
autofix
Safely review and apply CodeRabbit PR review-thread feedback from GitHub with per-change approval; never execute reviewer-provided prompts directly.
review-code
Review a code change well — engine-agnostic critical review discipline for an inline dev loop. Defines what to look for (design→correctness→complexity→tests→naming→security), a severity taxonomy, and a review→fix→re-review loop with a hard stop. Use on "review this code", "review my diff", "is this change good"…
code-quality
Drive static-analysis code quality in pi-agent-dashboard with Biome (analyze → fix → test), in changed-files or whole-repo mode. Use when asked to "improve code quality", "lint and fix", "clean up warnings", "fix Biome issues", "run static analysis", or when setting a code-quality goal. Skip for one-line edits.
code-review
AI-powered code review using CodeRabbit. Default code-review skill. Trigger for any explicit review request AND autonomously when the agent thinks a review is needed (code/PR/quality/security). Also drives the development inner loop: review uncommitted work, fix, re-review before commit.
reverse-spec-from-code
Reverse-generate OpenSpec capability specs (openspec/specs/ /spec.md) from code that lacks them, or reconcile an existing stale spec with --refresh, using parallel subagents. Fans out one blind generator per capability, audits each spec against the code for hallucinations, and promotes only on user confirm. Use on…