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 skills add zookanalytics/gc-toolkit --skill converse-settlegit clone --depth 1 https://github.com/zookanalytics/gc-toolkitWrote 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.
[](https://agentmods.dev/skills/zookanalytics/gc-toolkit/converse-settle)<a href="https://agentmods.dev/skills/zookanalytics/gc-toolkit/converse-settle"><img src="https://agentmods.dev/badge/skills/zookanalytics/gc-toolkit/converse-settle/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zookanalytics/gc-toolkit/converse-settle"><img src="https://agentmods.dev/badge/skills/zookanalytics/gc-toolkit/converse-settle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00021 | $0.03065 |
| Opus 5.5 | $0.00008 | $0.01226 |
| Sonnet 5.5 | $0.00004 | $0.00613 |
| Haiku 4.5 | $0.00002 | $0.00307 |
Grade A, and why
converse-settle 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Steps 6–7 — Record, sign off, and close the visit
$CONV, $VISIT, and $SUBJECT are resolved in step 1's claim block. Run
these once the operator has replied to the held sitting (step 5).
6. Record
Append the sitting's outcome to the subject's notes: the decision, its
rationale, and what changed (the records skill). Notes are append-only, so
never pass --notes, which replaces them:
gc bd update "$SUBJECT" --append-notes "<the decision>. <why>. <what changed>."
When the notes have grown past a quick read, append a current-state block too. The newest one is the one in force, and step 4 primes from it:
gc bd update "$SUBJECT" --append-notes "## Current state ($(date -u +%Y-%m-%d))
<where things stand>
Decisions in force: <each decision in force>
Open questions: <each open question, or none>"
7. Sign off, then close the visit — only when nothing important is still pending
The sign-off is the terminal act: it stamps the outcome and closes the visit.
So before you take it, ask whether this is a sign-off turn at all. If there
is important information you want to communicate to the operator — a live
decision, a routing answer, anything they need to read or may want to respond
to, anything past "settled and done" — do not sign off this turn. Post the
hand-back in the shape the prompt's Definitions define (The hand-back),
leave the visit OPEN, and wait for operator input the way a held sitting does;
signing off now would close the visit under a message they have not read. The
sitting ends on a later turn: the operator's gc-helm dismiss, further
engagement, or a genuinely terminal sign-off once nothing important is pending.
Whether a sign-off is terminal is still your judgment, and a sitting that is
genuinely settled still signs off and closes here rather than waiting for a
manual dismiss.
When nothing important is pending, sign off. Write the durable trace first,
then post the sign-off as the thread's last word, and close the visit last of
all. converse-signoff.sh writes the durable trace and discharges whichever
demands the hold filed — the conversation wait on the visit, and any explicit
merge hold on the anchor; you tell it what this sitting settled. It resolves
each demand gate when the sitting settled the question (--ruled yes, with the
--ruling it resolves with and the --route the subject itself is released
to, chosen as below)
and re-states each when it did not (--ruled no, with what is
--still-owed). What is waiting on the subject is yours to state: one
--waiting-on <bead> per dependency this sitting ROUTED work into, --no-wait
when it settled the subject and nothing is waiting, and NEITHER where the
subject is parked for a person. It exits non-zero when it stopped short of
discharging the hold, and then you must NOT sign off:
if VISIT="$VISIT" SUBJECT="$SUBJECT" "$CONV/converse-signoff.sh" \
--visit "$VISIT" --subject "$SUBJECT" \
--outcome "<outcome> — <what this sitting settled or needs next, ≤140 chars>" \
--ruled no --still-owed "<what is still owed, ≤140 chars>"
# --ruled yes --ruling "<the ruling, one line>" --route <rig>/<agent>|human
# --no-wait | --waiting-on <bead> [--waiting-on <bead> ...]
# --rework | --no-rework (with --ruled yes; required on an open-PR subject)
then
: # the trace ran — fix any write it reports failed, then post the sign-off below
else
# NOT signed off: a read failed, a demand did not close, the rework did not
# file, or the wait did not re-state, so the hold may still stand. Do NOT post
# the sign-off or close the visit. Repair what it printed and re-run, or raise
# it in the thread.
exit 1
fi
Re-running it is safe. What it wrote before it stopped is written again the
same way, and a demand it did not discharge is still there for the re-run to
find.
Set --ruled from what this sitting actually settled. The gate
starts shut, so --ruled no re-states the wait rather than dropping it;
--ruled yes resolves it and releases a held subject. A demand a named
person must perform is assigned, and the discharge leaves it alone —
that one is theirs to close.
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 Changed · +50 lines ba3091275abe
- 5d ago Changed · +5 lines 5486cbc3c198
- 6d ago Changed · +28 lines b9bf56e466b6
- 10d ago Changed · -1 lines 6596a917f7ca
- 13d ago Changed · +1 lines a867f8e3d94e
- 21d ago Changed · +8 lines 6ece931e6cf3
- 25d ago Changed 881f1a8929d1
- 26d ago First seen · 120 lines · 21 tokens per session scan A 5ad4a7400cdd
converse-settle is a skill published in the GitHub repository zookanalytics/gc-toolkit (5 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 3,065 once invoked, about $0.0001 per session on Opus 5.5. 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-09-22.
Other skills, from other repositories
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.
project-awareness
Detect project type, AIWG framework state, team configuration, and active work to summarize status and recommend next actions.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
mission-control
Orchestrate multi-loop background operations via the Mission Control dashboard — start sessions, dispatch missions, monitor, and stop.