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/spawnpoint-inc/spawnpoint-plugin/deploy-to-spawnpointnpx skills add spawnpoint-inc/spawnpoint-plugin --skill deploy-to-spawnpointgit clone --depth 1 https://github.com/spawnpoint-inc/spawnpoint-pluginWhat 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.00037 | $0.02803 |
| Opus 5 | $0.00018 | $0.01401 |
| Sonnet 5 | $0.00007 | $0.00561 |
| Haiku 4.5 | $0.00004 | $0.00280 |
Grade A, and why
deploy-to-spawnpoint 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.
seconds: `tar czf - --exclude .git --exclude node_modules . | curl -fsS -T - "<upload_url>"`. How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy to spawnpoint
Deploy a small app to spawnpoint. It runs the app on managed infrastructure and returns a
public URL. Use the deploy_project MCP tool.
When to use
The user wants to deploy / ship / launch / publish a small app, dashboard, tool, or prototype, and wants a shareable link.
How to deploy
Call deploy_project with:
name: a short slug for the project (e.g.standup-board).runtime:static(HTML/CSS/JS),node,python, ordocker. Defaultstatic. Fordocker, the bundle must include aDockerfileat its root; the machine builds and runs it, and the container must listen on port 8080 (PORT=8080is set). Reach for it when the app is a compiled language or needs system packages; prefer the other runtimes when one fits, since they skip the build and start faster.entrypoint: fornode/python, the file to run (defaultindex.js/main.py). Omit forstatic, and omit it for anodeproject that has astartscript: the deploy runsnpm startand abuildscript, so Next.js, Remix, Astro, Nuxt, SvelteKit, and Express deploy as themselves. Set it only to override a wrong script.files: an array of{ path, content }for every file in the app. Inline files are for apps you just wrote; for files already on disk, use the upload path below and passupload_idinstead.env: optional environment variables.visibility: new projects arerestrictedby default: only the owner and emails they share with (verified by a one-time code) can open the link. Passvisibility: "public"when the user asks for a link anyone can open, or flip it later withset_visibility. Tell the user which they got. To let specific people into a restricted project, callshare_projectwith each email: they get an invite email with the link, no account needed.
Files on disk? Upload, don't inline
Regenerating existing files as inline content is slow and expensive: an 80 KB site
is minutes of token generation, on every redeploy. When the app's files already exist
on disk (or the bundle is more than a few small text files, or contains any binary
asset like an image), use the upload transport instead:
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 · 188 lines · 37 tokens per session scan A 39a842526b13
deploy-to-spawnpoint is a skill published in the GitHub repository spawnpoint-inc/spawnpoint-plugin (0 stars, last pushed 18d ago), licensed MIT. It adds 37 tokens to every session and 2,803 once invoked, about $0.0002 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-31.
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…