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-environment-resolvergit 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-environment-resolver)<a href="https://agentmods.dev/skills/agent-clubhouse/goobers/goobers-environment-resolver"><img src="https://agentmods.dev/badge/skills/agent-clubhouse/goobers/goobers-environment-resolver/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-environment-resolver"><img src="https://agentmods.dev/badge/skills/agent-clubhouse/goobers/goobers-environment-resolver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 170 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00046 | $0.03943 |
| Opus 5 | $0.00023 | $0.01972 |
| Sonnet 5 | $0.00009 | $0.00789 |
| Haiku 4.5 | $0.00005 | $0.00394 |
Grade A, and why
goobers-environment-resolver 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.
How it starts
The opening of the file, as written. The whole thing — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goobers environment resolver
Establish which Goobers release and release-owned contracts govern the current work. Perform this resolution before authoring configuration, interpreting a run, or planning an upgrade.
Treat the config repository, initialized instance, Goobers source checkout, and target application repositories as separate locations. Never infer that one repository has another role without marker or structured-config evidence.
Safety boundary
Use read-only filesystem, Git, Goobers, and provider commands. Do not install,
build, clone, fetch, pull, checkout, start a daemon, or run target-repository
scripts. Do not read environment dumps, credential helpers, .env files, token
files, secret stores, or paths named by credential references. Do not print raw
Git remote URLs, which may contain user information.
Inspect only caller-supplied paths, the current repository and its ancestors, the selected instance, the exact config-source path declared by that instance, and configured target repositories. Missing, inaccessible, or competing paths are unresolved; they do not authorize a broad search of parent or sibling directories.
Resolution procedure
1. Record the environment locations
Find the current Git root without reading remotes:
git -C <start> rev-parse --show-toplevel
To determine whether that root is a configured target, use an in-process repository-identity helper. The helper must capture both stdout and stderr when invoking Git rather than inherit them: first enumerate remote names, then capture the fetch URLs for each name. Do not run the URL-producing Git command directly through a terminal or tool invocation that displays, records, or returns raw command output.
While the captured bytes remain private to the helper, parse each URL into a
credential-free provider key. Accept GitHub URL forms only as
github/<owner>/<name> and Azure DevOps URL forms only as
ado/<organization>/<project>/<name>; discard scheme, user information, port,
query, fragment, and a terminal .git. Normalize provider host and
provider-defined case-insensitive identity components. The helper may return or
print only normalized provider keys, never raw URLs or parse errors containing
them. If recognized remotes produce zero or multiple distinct identities,
report the current repository identity unresolved. Match a target only when the
entire sanitized provider key equals the key from structured config; a
repository name or owner/name suffix alone is not evidence.
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 · 354 lines · 46 tokens per session scan A 7263dbab070a
goobers-environment-resolver is a skill published in the GitHub repository Agent-Clubhouse/Goobers (6 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 3,943 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…