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 recordsgit 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/records)<a href="https://agentmods.dev/skills/zookanalytics/gc-toolkit/records"><img src="https://agentmods.dev/badge/skills/zookanalytics/gc-toolkit/records/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/records"><img src="https://agentmods.dev/badge/skills/zookanalytics/gc-toolkit/records.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.00100 | $0.00810 |
| Opus 5.5 | $0.00040 | $0.00324 |
| Sonnet 5.5 | $0.00020 | $0.00162 |
| Haiku 4.5 | $0.00010 | $0.00081 |
Grade A, and why
records 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Records: what a bead's next reader inherits
A bead carries its own record. The next worker, sitting or person who reads it starts from what is written there, not from your context, which ends with your session. Each option says what the record means, who reads it, and the one writer that sends it.
The writers are the gc-toolkit pack's own scripts.
gc <binding> scripts-dir prints their directory in the pack as gc loaded it,
so each example calls the pack's copy inside the command itself, and runs in a
fresh shell. <binding> is the name the city imports the pack under, which gc
puts in front of this skill's name: gc-toolkit in gc-toolkit.records.
gc skill list prints it in this skill's FROM column.
Record an outcome on a bead
The message is what was decided or found, why, and what changed. The next reader of the bead picks it up: a sitting primes from the bead's notes, and a worker reads them before it starts.
Writer: gc bd update <bead> --append-notes "<decision or finding, the reason, what changed>".
Notes are append-only. --notes replaces the whole field and erases every
note other writers left there, so never use it.
When the notes have grown past a quick read, append a current-state block: where things stand, the decisions in force, and the open questions. The newest current-state block is the one in force, so a reader starts there:
gc bd update <bead> --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>"
A bead's notes are operational state. A durable document, such as a spec, an analysis or a decision record, is a file in a repo, filed through the filing-documentation skill. A sitting writes no files, so it files a bead for the document instead (the work skill).
Set the headline the board shows
The message is one sentence saying what the bead needs now. The helm board
shows it as the bead's NEEDS cell, and doctor/check-wait-is-an-edge checks
the wait it declares against the bead's blocks edges.
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 · 64 lines · 100 tokens per session scan A 43a9bfc20d2a
records is a skill published in the GitHub repository zookanalytics/gc-toolkit (5 stars, last pushed today), licensed MIT. It adds 100 tokens to every session and 810 once invoked, about $0.0004 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-10-17.
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.