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/generous-corp/pulp/prototype-loopnpx skills add Generous-Corp/pulp --skill prototype-loopgit clone --depth 1 https://github.com/Generous-Corp/pulpWrote 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/generous-corp/pulp/prototype-loop)<a href="https://agentmods.dev/skills/generous-corp/pulp/prototype-loop"><img src="https://agentmods.dev/badge/skills/generous-corp/pulp/prototype-loop.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.00068 | $0.02184 |
| Opus 5 | $0.00034 | $0.01092 |
| Sonnet 5 | $0.00014 | $0.00437 |
| Haiku 4.5 | $0.00007 | $0.00218 |
Grade A, and why
prototype-loop 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 today.
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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prototype Loop Skill
Codifies the leveraged-prototype dev loop for closing framework gaps during high-feedback UI parity work.
When to use this skill
Trigger this skill when the user is doing any of:
- Porting a UI to Pulp and wants tight visual-feedback iteration (Spectr's WebView editor → native via
@pulp/reactis the canonical example). - Gap-finding — they suspect there are framework gaps and want to enumerate them via an AOT analyzer.
- Multi-PR upstream coordination — they're filing a batch of framework PRs and want a tight loop while upstream merges land.
- Hitting slow cross-platform configure cost (Skia/Dawn/threejs FetchContent) on changes that only need single-platform validation during iteration.
Do not trigger for: bugfixes, cross-platform refactors, or final-landing flows. Those want the cross-platform default.
When NOT to use this skill
- Pre-merge / landing the consumer's PR — always exit focus mode (or run
shipyard pr/pulp pr) before landing. The ship path validates cross-platform regardless, but exiting focus mode keeps subsequent local iteration honest. - Bugfixes that touch platform-specific code — a cross-platform build is the cheapest correctness check for those.
- Refactors that span subsystems — single-platform configure can mask a build break on a sibling platform.
The loop in one breath
analyze → file → prototype (ar-swap) → monitor → bump → ship
Each step has tooling. The CLI loop is available now; deeper archive-splice, issue-monitoring, and analyzer-lift work should land separately.
Current surface
| Surface | Status |
|---|---|
pulp loop CLI + skill + slash command + docs |
available |
pulp-ar-swap.sh ABI-checked archive splice |
deferred |
pulp loop --watch-issues PR-monitor |
deferred |
Lift @pulp/css-adapt, pulp-css-analyze, extract-html-bundle |
deferred |
Step 1 — AOT analyze the consumer's bundle
Run pulp-css-analyze over the consumer's pre-built React bundle. The output is a coverage report listing unmapped CSS props with occurrence counts.
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.
- today First seen · 160 lines · 68 tokens per session scan A 99d1f7efd0e6
prototype-loop is a skill published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 2,184 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…