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/jerpint/woltspace/migrate-to-projectsnpx skills add jerpint/woltspace --skill migrate-to-projectsgit clone --depth 1 https://github.com/jerpint/woltspaceWrote 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/jerpint/woltspace/migrate-to-projects)<a href="https://agentmods.dev/skills/jerpint/woltspace/migrate-to-projects"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/migrate-to-projects.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.01111 |
| Opus 5 | $0.00021 | $0.00556 |
| Sonnet 5 | $0.00008 | $0.00222 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
migrate-to-projects 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 4d 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.
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate to Projects
Your human (or a previous session) edited files in /workspace/woltspace/ — the platform code. This causes problems: when the platform updates, those changes get overwritten or cause merge conflicts. Your job is to safely extract their work into wolt/apps/ and restore the platform to a clean state.
Be careful. This is a recovery operation. Don't lose anyone's work.
Step 1: Assess the damage
Check what's been modified in the platform directory:
cd /workspace/woltspace
git status
git diff --stat
Categorize the changes:
- User code — new files, new features, apps they built (these need to be saved)
- Config tweaks — changes to server.js, entrypoint, bot code (these need to be understood, then discarded)
- Untracked files — new files that aren't part of the platform (likely user work)
Tell the human what you found. Be specific: "You have 3 modified files and 5 new files in the platform directory. Here's what I see..."
Step 2: Extract user work
For each piece of user work you find:
- Create an app directory:
mkdir -p wolt/apps/{name} - Copy the files there:
cp -r /workspace/woltspace/{path} wolt/apps/{name}/ - If it's an app that was running on a port, note the port in woltspace.json
- If it depends on platform code (imports from server.js, etc.), refactor those dependencies out — the app should be self-contained
Example extractions:
- Custom API endpoint added to server.js → extract into its own FastAPI/Express server in an app
- Modified bot behavior → document what they wanted in a memory file, suggest filing an issue
- New HTML pages in public/ → move to wolt/site/ or an app
- New scripts in container/bin/ → move to an app
Step 3: Document config changes
Some changes are config tweaks rather than new code. For these:
- Note what was changed and why (ask the human if unclear)
- Check if there's a proper way to achieve the same thing (env vars, wolt-specific overrides, skill customization)
- If it's a legitimate feature request, suggest filing an issue on the woltspace repo
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.
- 4d ago First seen · 131 lines · 42 tokens per session scan A 1ef4750dd7f4
migrate-to-projects is a skill published in the GitHub repository jerpint/woltspace (11 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 1,111 once invoked, about $0.0002 per session on Opus 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-08-30.
Other skills, from other repositories
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.