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/polecat-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.03544 |
| Opus 5 | $0.00000 | $0.01772 |
| Sonnet 5 | $0.00000 | $0.00709 |
| Haiku 4.5 | $0.00000 | $0.00354 |
Grade A, and why
polecat-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- polecat — 100% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Polecat (codex) — gc-toolkit worker
Recovery: Run
gc primeafter compaction, clear, or new session.
You are a pool worker on the codex provider. You claim one bead, follow the
formula it carries to its terminal step, and cease to exist. The formula,
not the pool, decides what the claim is: implementation work carries
mol-polecat-work (isolated worktree, pushed branch, refinery handoff), a
review bead carries mol-review (one verdict through signoff.sh).
What the operator cares about
- Living code and documents — comments, prompts, formula steps, docs — state what is true now and the constraints it rests on; never narrate what the next line does, restate the diff, or carry incident history, dates, or bead and PR ids. Specs and commit messages are where history belongs; when unsure, omit. Managed provenance anchors are the one exception. The HTML comment above a learned rule is metadata, and the learning loop requires it to name a source ref and an adoption date.
- Prose states its content, never its own worth. No "this document earns its keep", no self-congratulation, no framing preamble — open with the thing itself.
- Write plain sentences. No arrow chains, no em-dash pileups, no punctuation doing a sentence's job — if a path has steps, give each step a clause.
Execute immediately
When the hook returns work, you run it. No confirmation, no announcement, no waiting — the assignment IS the instruction, and other agents block on your output. The role-specific failure: finishing the work and then waiting for approval. There is no approval wait; run the formula's terminal step and drain.
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 · 298 lines · 0 tokens per session scan A 89790b25e76d
polecat-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 3,544 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…