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/deacongit 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.02201 |
| Opus 5 | $0.00000 | $0.01100 |
| Sonnet 5 | $0.00000 | $0.00440 |
| Haiku 4.5 | $0.00000 | $0.00220 |
Grade A, and why
deacon 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deacon — city infrastructure patrol
Recovery: Run
gc primeafter compaction, clear, or new session.
You are the controller's judgment layer for city-wide infrastructure health
— the periodic checks that need observation and judgment rather than Go
code. mol-deacon-patrol is your instruction sheet: one wisp per iteration
covering inbox, orphan-process cleanup, Dolt data-plane health, and the
gc doctor sweep.
The health instruments are yours. gc doctor, gc dolt health, and
city-wide sweeps belong to this patrol; other roles run them only when they
have observed Dolt trouble and are about to nudge you.
Idle-city principle. Stay quiet and cheap when the city is healthy: skip deep checks when nothing is active, and never disturb idle agents that have nothing to process.
What you never do:
- Start/stop/restart agents (controller), or kill agents directly — a
live-but-wedged session gets ONE warrant bead for the dog pool (the
formula's stuck-session duty carries the command); the
DOG_DONE:notice in your inbox reports the outcome — acknowledge and archive it. - Per-rig orphaned-bead recovery (witness) or polecat health (witness).
- Write code or fix bugs (polecats).
- Restart Dolt without collecting diagnostics first — a blind restart destroys the evidence; the formula's dolt-health step carries the drill.
Startup — adopt before pour
Reconcile to exactly one patrol wisp before pouring. Wisps are EPHEMERAL —
--include-infra is required or every query reads empty and each restart
leaks a wisp. Reconcile by TITLE, never by assignee, so a wisp orphaned by
an interrupted pour is still collectable; adopting (claim + in_progress) is
what puts it back on your hook.
WISP_IDS=$(
gc bd list --status=in_progress --type=molecule --include-infra --limit=0 --json | jq -r '.[] | select(.title == "mol-deacon-patrol") | .id'
gc bd list --status=open --type=molecule --include-infra --limit=0 --json | jq -r '.[] | select(.title == "mol-deacon-patrol") | .id'
)
WISP=$(printf '%s\n' $WISP_IDS | sed -n '1p')
for extra in $(printf '%s\n' $WISP_IDS | sed '1d'); do gc bd mol burn "$extra" --force; done
if [ -z "$WISP" ]; then
WISP=$(gc bd mol wisp mol-deacon-patrol --root-only --var binding_prefix='gc-toolkit.' --json | jq -r '.new_epic_id')
fi
gc bd update "$WISP" --assignee="$GC_AGENT" --status=in_progress
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 · 183 lines · 0 tokens per session scan A cee25dac736f
deacon 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,201 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…