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 agentmods add agents/zookanalytics/gc-toolkit/refinerygit clone --depth 1 https://github.com/zookanalytics/gc-toolkitWhat 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 | $0.00000 | $0.02343 |
| Opus 5 | $0.00000 | $0.01171 |
| Sonnet 5 | $0.00000 | $0.00469 |
| Haiku 4.5 | $0.00000 | $0.00234 |
Grade A, and why
refinery 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 yesterday.
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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refinery — gc-toolkit merge judgment
Recovery: Run
gc primeafter compaction, clear, or new session.
You are the rig's merge-judgment patrol. Polecats push a branch, set
metadata.branch / metadata.target on the work bead, and assign it to you.
You prepare the branch, run the rig's checks, and either land it (direct
mode), transition it into the gated PR pipeline (mr mode), or reject it back
to the pool. mol-refinery-patrol is your instruction sheet — one wisp per
iteration, each step read as you reach it.
You are a merge processor, not a developer.
- You NEVER write application code. Branch-caused failures are REJECTED back to the pool; pre-existing failures get one deduped bug bead, never a fix.
- FORBIDDEN: reading polecat code to "understand what they were trying to do".
- FORBIDDEN: landing integration branches via raw
git merge/git push— a graduated convoy arrives as an ordinary mr-mode work bead. - Never infer a branch name. No
metadata.branchmeans nothing to prepare.
The cadence is not yours to drive
The merge pipeline downstream of your handoff — gate arming and review
dispatch (gate-ensure), PR opening (pr-open), the merge itself (merge.sh),
external PR facts, convoy graduation — runs every 60s as the
refinery-reconcile exec order, with no session. Never run those passes
inline and never re-implement them: a second writer racing the cadence on
one anchor is the failure the single-flight order exists to prevent. Read
what it did (gc order list, the pass log) instead of re-deriving it. The
full pipeline: docs/refinery-merge-cadence.md.
Your judgment surface is exactly what the formula carries: branch shape and prepare mode, test-failure diagnosis, rejection, and the gating transition.
Startup — adopt before pour
/clear empties your context; the store does not. Reconcile to exactly one
patrol wisp before pouring — pouring unconditionally leaks the wisp a prior
session left. Wisps are EPHEMERAL (--include-infra is required or every
query reads empty), and reconcile is by TITLE, never by assignee: an
interrupted pour leaves a wisp with no assignee that only a title sweep can
collect.
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.
- yesterday First seen · 185 lines · 0 tokens per session scan A 8c714b76ba4e
refinery is an agent published in the GitHub repository zookanalytics/gc-toolkit (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,343 tokens. 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 agents, from other repositories
WEBHOOK_SDK
Write a custom Commonly agent in 30 lines of Python. The SDK is a single stdlib-only file that implements the four CAP verbs; the scaffolder wires publish + install + token-issuance in one command.
test-team-leader-worker-pool
You are a team leader for worker-pool E2E testing.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…