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 skills/steipete/agent-scripts/clickclacknpx skills add steipete/agent-scripts --skill clickclackgit clone --depth 1 https://github.com/steipete/agent-scriptsWhat 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.00024 | $0.00813 |
| Opus 5 | $0.00012 | $0.00407 |
| Sonnet 5 | $0.00005 | $0.00163 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
clickclack scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl -s https://clickclack.chat/ | grep -oE 'entry/app\.[A-Za-z0-9_-]+\.js'` — hash must match the freshly deployed build (compare against `https://clickclack.services-91b.workers.dev`). How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClickClack
Use this for ClickClack product/runtime ops, deploys, hosted app checks, and domain questions.
What
- Repo:
~/Projects/clickclack/https://github.com/openclaw/clickclack - Product: self-hostable Slack-style chat for OpenClaw/community/agent workflows.
- Surfaces:
https://clickclack.chatproduct site (Cloudflare Worker custom domain)https://www.clickclack.chat(Worker custom domain, same worker)https://app.clickclack.chathosted app (Worker custom domain)https://docs.clickclack.chatGitHub Pages docs fromdocs/
Prod (Cloudflare, since 2026-07-05)
- Everything is one Cloudflare Worker
clickclackin the OpenClaw account (91b59577e757131d68d55a471fe32aca) fronting a Cloudflare Container. - Worker + container config:
wrangler.jsonc(routes are declarativecustom_domainentries). - Container: Go binary + embedded SPA from
Dockerfile.cloudflare; data in Supabase Postgres (CLICKCLACK_DBsecret) and R2 uploads (clickclack-uploads). - Zone
clickclack.chatide7f93ba1ec24d75ce60c468bbaba5cb5(OpenClaw account).docsCNAME →openclaw.github.iostays DNS-only. - 1Password (OpenClaw vault): "Cloudflare ClickClack deploy token" (
api_tokenfield, workers-scoped; no DNS edit), "Cloudflare ClickClack R2 uploads". - Legacy Hetzner box
clickclack-prod-01(157.90.237.80) no longer serves any DNS; decommission when confident. Old runbook in git history of this file.
Deploy
cd ~/Projects/clickclack && git pull --ff-only- Docker must run (OrbStack:
open -a OrbStack). pnpm deploy:cloudflare(auth:wrangler loginOAuth or the 1Password deploy token asCLOUDFLARE_API_TOKEN).- Rollout gotcha: the running container instance is NOT replaced while it has traffic;
sleepAfter=10mnever fires on a public site. BumpCLICKCLACK_CONTAINER_NAMEinwrangler.jsonc(dated, e.g.prod-YYYYMMDD-open-org) and redeploy to force a fresh instance on the new image. Container is stateless (Postgres/R2), so the swap is safe. - Commit the
wrangler.jsoncbump.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 49 lines · 24 tokens per session scan A e7c85b06b19e
clickclack is a skill published in the GitHub repository steipete/agent-scripts (6,580 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 813 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…