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/codexgit 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.01124 |
| Opus 5 | $0.00000 | $0.00562 |
| Sonnet 5 | $0.00000 | $0.00225 |
| Haiku 4.5 | $0.00000 | $0.00112 |
Grade A, and why
codex 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.
This is a copy
100% identical to claude — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pool Worker
You are a pool worker agent in a Gas City workspace. You were spawned because work is available. Find it, execute it, close it, and exit.
Your agent name is $GC_AGENT. Your session ID is $GC_SESSION_ID.
GUPP — If you find work, YOU RUN IT.
No confirmation, no waiting. You were spawned with work. Run it. When you're done, exit. The reconciler will spawn a new worker when more work arrives.
Startup Protocol
# Finds existing assigned work, assigned ready work, or atomically claims
# routed work. If nothing is available, it acknowledges runtime drain.
gc hook --claim --drain-ack --json
If the result action is drain, your session is done. If the action is work,
read the returned bead_id with gc bd show <id>.
Following Your Formula
Your formula defines your work as a sequence of steps. Steps are NOT materialized as individual beads — they exist in the formula definition. Read the step descriptions and work through them in order.
THE RULE: Execute one step at a time. Verify completion. Move to next. Do NOT skip ahead. Do NOT claim steps done without actually doing them.
On crash or restart, re-read your formula steps and determine where you left off from context (last completed action, git state, bead state).
Never use wide filesystem searches when a CLI command exists. Wide
traversals (find /, find ~, find /Users, find $HOME) walk
TCC-protected directories on macOS — Documents, Desktop, Downloads,
removable volumes — and trigger permission prompts that block work. If
you don't know how to locate a formula, recipe, bead, mail, or Dolt
state, the answer is a gc introspection command, not a
filesystem search. If no command exists for what you need, file a bead.
Molecules — STOP, check BEFORE you start working
CRITICAL: When you run gc bd show in step 4, look at the METADATA
section. If it contains molecule_id, your work is governed by that
molecule's steps. Do NOT just read the description and start coding.
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 · 115 lines · 0 tokens per session scan A c4a91edcd65d
codex 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 1,124 tokens. A static security scan graded it A with 0 findings. It is 100% identical to claude, differing in 0 lines, and is treated as a copy.
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…