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/nirholas/three.ws/register_flowgit clone --depth 1 https://github.com/nirholas/three.wsWhat 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.01933 |
| Opus 5 | $0.00000 | $0.00966 |
| Sonnet 5 | $0.00000 | $0.00387 |
| Haiku 4.5 | $0.00000 | $0.00193 |
Grade A, and why
REGISTER_FLOW 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Registration Flow — Server-side Prep + Client-side Sign
Overview
ERC-8004 agent registration is a two-step flow that keeps the private key on the client:
- Prep (server): Build canonical JSON, pin to IPFS, store transient record → get CID
- Sign (client): Sign the registration tx, submit to blockchain
- Confirm (server): Verify tx succeeded, metadata CID matches, update database
The server-side prep endpoint eliminates the need for users to manage IPFS pinning tokens (web3.storage / Filebase), while keeping blockchain operations fully client-controlled.
Sequence Diagram
┌────────┐ ┌──────────────┐ ┌─────────────────┐
│ Client │ │ Our Servers │ │ IPFS / Blockchain│
└───┬────┘ └──────┬───────┘ └────────┬────────┘
│ │ │
│ 1. POST /api/agents/register-prep │ │
│ {name, description, avatarId, ...} │ │
├─────────────────────────────────────────>│ │
│ │ │
│ (validate input, │ │
│ build JSON, │ │
│ pin to IPFS) │ │
│ │ │
│ ├────────────────────────────────>│
│ │ Pin registration.json │
│ │<────────────────────────────────┤
│ │ CID returned │
│ │ │
│ (store prep record,│ │
│ 1-hour expiry) │ │
│<─────────────────────────────────────────┤ │
│ {ok: true, cid, metadataURI, prepId} │ │
│ │ │
│ 2. Sign tx locally │ │
│ (registerAgent(owner, metadataURI)) │ │
│ │ │
│ 3. Submit tx to blockchain │ │
│────────────────────────────────────────────────────────────────>│
│ │ │
│ │ (wait for confirmation)
│<─────────────────────────────────────────────────────────────────┤
│ tx.hash returned │ │
│ │ │
│ 4. POST /api/agents/register-confirm │ │
│ {prepId, chainId, agentId, txHash} │ │
├─────────────────────────────────────────>│ │
│ │ │
│ (fetch tx receipt,│ │
│ parse event, │ │
│ verify CID match)│ │
│ ├────────────────────────────────>│
│ │ getTransactionReceipt(txHash) │
│ │<────────────────────────────────┤
│ │ Receipt with logs │
│ │ │
│ (upsert agent_ │ │
│ identities, │ │
│ consume prep) │ │
│<─────────────────────────────────────────┤ │
│ {ok: true, agentId} │ │
│ │ │
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 · 228 lines · 0 tokens per session scan A 87f7e92e3458
REGISTER_FLOW is an agent published in the GitHub repository nirholas/three.ws (107 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,933 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-30.
Other agents, from other repositories
blender-artist
3D and 2D visualization specialist using Blender Python API for scene creation, procedural modeling, animation, rendering, and 2D composition.
director
Turn a request into a shot-plan.json for a short (3–30s) design-led motion graphic. You run in two parts around the asset-sourcing step: Part 1 (plan) before sourcing, Part 2 (design) after. You do NOT write composition code — that's the Builder. Schema: references/shot-plan-ir.md.
AGENTS.motiscope
Agent "AGENTS.motiscope" from KumarSashank/motiscope, covering motiscope — recreate animations from screen recordings, the division of labor, commands and workflows.
svg-verifier
Visually verify a rendered SVG animation in chrome-devtools MCP and return a tight verdict (≤100 words). Specialized for the /svg-verify skill's isolated-context phase. Use when the calling thread needs an objective read on motion / timing / quality without drowning in screenshot bytes.
svg-explorer
Generate N stylistic variants of one SVG animation request in parallel and return a tight comparison summary. Use when the user asks for "options", "a few variants", "show me some styles", or when /svg-animate decides that exploring axes beats single-shot composition.
Demonstrate
Agent for demonstrating VS Code features.