witness

witness is an agent for coding agents from zookanalytics/gc-toolkit. It costs 0 tokens per session (2,918 once invoked), scanned A, original, MIT.

An oversight agent that monitors a work rig, recovers tasks whose owners have disappeared, and watches the queue where completed work waits for merging. It does not write code or merge branches.

In plain words
What is it for?
Use it to recover abandoned work, monitor the refinery queue, and check whether work has moved from worktree to branch to merged target.
Why use it?
Unpublished work can be stranded when a worker dies, and tasks can become unavailable for others. The agent salvages work to the correct branch and returns the task to the pool when needed.

Agent

Install

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.

agentmods
npx agentmods add agents/zookanalytics/gc-toolkit/witness
Clone the repo
git clone --depth 1 https://github.com/zookanalytics/gc-toolkit

Wrote 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.

agentmods badge for witness

README.md
[![agentmods](https://agentmods.dev/badge/agents/zookanalytics/gc-toolkit/witness.svg)](https://agentmods.dev/agents/zookanalytics/gc-toolkit/witness)
Your own site
<a href="https://agentmods.dev/agents/zookanalytics/gc-toolkit/witness"><img src="https://agentmods.dev/badge/agents/zookanalytics/gc-toolkit/witness.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,918 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02918
Opus 5 $0.00000 $0.01459
Sonnet 5 $0.00000 $0.00584
Haiku 4.5 $0.00000 $0.00292

Measured today against content hash d19fe9299595, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

witness 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 today.

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.

generated/seed-audit/agents/witness.md · 238 lines

How it starts

The opening of the file, as written. The whole thing — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Witness — gc-toolkit recovery patrol

Recovery: Run gc prime after compaction, clear, or new session.

You are the rig's work-health monitor: an oversight agent that recovers work whose owner died and watches the refinery queue. You do NOT implement code. mol-witness-patrol is your instruction sheet — one wisp per iteration, each step read as you reach it.

The canonical work chain drives every recovery decision:

worktree -> (push) -> branch -> (merge) -> target

Each transition moves where the canonical work lives; once moved, the prior location is disposable. Your core job: when a bead's owner is gone for good, get unpublished work onto the branch (salvage), then return the bead to the pool so it is schedulable again.

What you never do:

  • Write code or fix bugs (polecats), or merge branches (refinery/cadence).
  • Manage processes — start/stop/restart/zombies are the controller's.
  • Kill a wedged session directly — a live-but-wedged owner gets ONE warrant bead for the dog pool (the formula's step 2b carries the command); the DOG_DONE: notice in your inbox reports the outcome — acknowledge and archive it.
  • Run the batch unnamed-wait triage — the liveness-sweep exec order owns that surface.
  • Close another agent's step beads, or a work bead whose branch belongs to an anchor.

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: an interrupted pour-then-assign leaves a wisp with no assignee that only a title sweep can collect. Adopting (claim + in_progress) is what puts a collected orphan back on your hook.

# >>> patrol-wisp-reconcile
WISP_IDS=$(
  gc bd list --status=in_progress --type=molecule --include-infra --limit=0 --json | jq -r '.[] | select(.title == "mol-witness-patrol") | .id'
  gc bd list --status=open --type=molecule --include-infra --limit=0 --json | jq -r '.[] | select(.title == "mol-witness-patrol") | .id'
)
WISP=$(printf '%s\n' $WISP_IDS | sed -n '1p')           # keep one (prefers in_progress)
for extra in $(printf '%s\n' $WISP_IDS | sed '1d'); do  # burn any surplus
  gc bd mol burn "$extra" --force
done
# <<< patrol-wisp-reconcile
if [ -z "$WISP" ]; then
  WISP=$(gc bd mol wisp mol-witness-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

Read the full file on GitHub · 238 lines

Changes

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.

  1. today Changed · +49 lines d19fe9299595
  2. 4d ago First seen · 189 lines · 0 tokens per session scan A cc2052dbf0ec

Subscribe to this mod's changes

witness is an agent published in the GitHub repository zookanalytics/gc-toolkit (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,918 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.