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 Agent-Clubhouse/Goobers --skill goobers-workflow-upgradegit clone --depth 1 https://github.com/Agent-Clubhouse/GoobersWrote 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/agent-clubhouse/goobers/goobers-workflow-upgrade)<a href="https://agentmods.dev/skills/agent-clubhouse/goobers/goobers-workflow-upgrade"><img src="https://agentmods.dev/badge/skills/agent-clubhouse/goobers/goobers-workflow-upgrade/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/agent-clubhouse/goobers/goobers-workflow-upgrade"><img src="https://agentmods.dev/badge/skills/agent-clubhouse/goobers/goobers-workflow-upgrade.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.00041 | $0.02538 |
| Opus 5 | $0.00020 | $0.01269 |
| Sonnet 5 | $0.00008 | $0.00508 |
| Haiku 4.5 | $0.00004 | $0.00254 |
Grade A, and why
goobers-workflow-upgrade 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.
How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goobers workflow upgrade
Assess first and write only when the user explicitly requests it. Never silently
bump a dslVersion, replace a custom workflow with a template, start a workflow,
materialize runtime configuration, or change daemon state.
Resolve the current environment with goobers-environment-resolver before doing
anything else. Resolve the selected target release separately when it differs
from the current binary. The target binary, contracts, docs, schemas, examples,
feature data, and migration tooling must all have the same exact release
identity. For a stable release use its exact tag and commit; for a pre-release or
source build use its exact commit. The default branch is never an authoritative
upgrade source.
1. Establish the upgrade boundary
Record these locations and identities from the resolver report:
- the config source and the active
<instance>/configruntime copy; - the current and target executable paths, versions, and commits;
- the current and target
dslVersions[]support matrices; - the verified current and target contract roots;
- whether the config source is a local directory, a local Git ref, or remote;
- every workflow file, its explicit
dslVersion, and its owning gaggle.
Keep the effective config source, active runtime copy, and write target as
separate identities. A writable kind: local-dir source may be the write
target. A kind: git source is the committed configured ref, not whichever
branch or working tree is present at its local path, so it is analysis-only by
default. It may have a write target only when the user explicitly selects and
approves an authoring worktree whose clean HEAD equals the resolver's full
source commit and whose checked-out branch is exactly the configured ref.
Remote, unavailable, unresolved, or otherwise unwritable sources remain
analysis-only. The active runtime copy is evidence only unless the resolver
proves it is also the effective source.
Use a disposable scratch instance when a command requires an instance root but
the selected source is a checked-in source tree. Copy manifest.yaml and
gaggles/ into the scratch instance's config/; do not rewrite the real source
just to satisfy a command's expected layout. Record that scratch derivation in
the report.
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 · 237 lines · 41 tokens per session scan A 291aa3bdb20c
goobers-workflow-upgrade is a skill published in the GitHub repository Agent-Clubhouse/Goobers (6 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 2,538 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…