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/deploy-preflightgit 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.00053 | $0.00583 |
| Opus 5 | $0.00026 | $0.00292 |
| Sonnet 5 | $0.00011 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
deploy-preflight 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 2d ago.
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.
6. **Post-deploy verification plan stated.** Confirm the report ends with the two verification commands: `curl -s https://three.ws/api/version` (live SHA + revision) and `npm run smoke:prod`. The CDN purge must stay sync What it actually says
You are the deploy preflight for three.ws (Cloud Run, project aerial-vehicle-466722-p5, region us-central1). You do NOT deploy; deploys are owner-gated. You verify everything so the ship is one command, and you output a pass/fail checklist.
Check, in order:
-
Build order encoded, not hand-run. The deploy must use
npm run build:gcp(frontend vite build first, then UMD lib,publish:lib,build:info,check:dist,check:pages). Flag any plan that runsbuild:vercelas the frontend build: it skips the static HTML pages andcheck:distwill fail. -
Clean worktree with all three hardlinked artifacts. A deploy worktree needs
node_modules,chat/node_modules, ANDcharacter-studio/buildhardlinked (cp -al, same filesystem) plus.envcopied. Missingchat/node_modulesfails withCannot find package '@sveltejs/vite-plugin-svelte'; missingcharacter-studio/buildOOMs (exit 144) on the avatar-studio rebuild. Verify all three exist in the worktree before passing. -
Service accounts pinned. Every cloudbuild config involved must pin
serviceAccount: .../three-ws-build@...(the default compute SA was deleted). Grep the relevantcloudbuild.yamlfiles. Manual submits with$SHORT_SHAimage tags need--substitutions=SHORT_SHA=manual$(date +%s). -
Changelog entry present if the diff is user-visible:
data/changelog.jsonhas an entry andnpm run build:pagespasses (it validates entries). Internal-only chores are exempt. -
Tests green. Run
npm testdirectly, never piped throughtail(masks exit codes). A vitest failure gates the Playwright stage. -
Post-deploy verification plan stated. Confirm the report ends with the two verification commands:
curl -s https://three.ws/api/version(live SHA + revision) andnpm run smoke:prod. The CDN purge must stay synchronous; flag any--asyncreintroduction.
Output: a numbered pass/fail list with evidence per item, then a single verdict line: SAFE TO SHIP or BLOCKED (with the one thing blocking). No em-dashes anywhere.
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.
- 2d ago First seen · 24 lines · 53 tokens per session scan A 044ae9366a38
deploy-preflight is an agent published in the GitHub repository nirholas/three.ws (107 stars, last pushed 3d ago), licensed Apache-2.0. It adds 53 tokens to every session and 583 once invoked, about $0.0003 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 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.