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/view-bridgenpx skills add Generous-Corp/pulp --skill view-bridgegit 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/view-bridge)<a href="https://agentmods.dev/skills/generous-corp/pulp/view-bridge"><img src="https://agentmods.dev/badge/skills/generous-corp/pulp/view-bridge.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.1 | $0.00046 | $0.32799 |
| Opus 5 | $0.00023 | $0.16400 |
| Sonnet 5 | $0.00009 | $0.06560 |
| Haiku 4.5 | $0.00005 | $0.03280 |
Grade C, and why
view-bridge scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$CONSUMER/build/CMakeFiles/<your-target>.dir" How it starts
The opening of the file, as written. The whole thing — 2,305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ViewBridge skill
TL;DR. Every Pulp plugin format adapter (VST3, AU v2, AU v3, CLAP,
AAX, Standalone) opens its editor through
pulp::format::ViewBridge. You only touch the bridge when you override
Processor::create_view() or write a new adapter. This skill captures
the invariants the API enforces and the pitfalls that bit us enough
times to be worth remembering.
When to use ViewBridge
| Task | Touch ViewBridge? |
|---|---|
| Add a knob to the auto-generated editor | No — just define_parameters |
Return a hand-built view::View tree from a processor |
Yes — override Processor::create_view() |
| React when the host actually shows / resizes / closes the editor | Yes — override on_view_opened / on_view_closed / on_view_resized |
| Add a new format adapter | Yes — construct a ViewBridge and follow the lifecycle protocol |
| Hand the built view to an external container (TabPanel, WindowHost) | Yes — call ViewBridge::release_view() |
| Ship a paint-only overlay | No — the legacy standalone inspector runtime was removed; compose canonical control separately |
Native scripted UI is not a WebView
ScriptedUiSession, WidgetBridge, and @pulp/react execute through Pulp's JS
engine and native Skia/Dawn view tree; they do not require WebViewPanel. In an
SDK configured with PULP_BUILD_WEBVIEW=ON, use pulp::view-native (or
pulp_add_plugin(... NATIVE_UI), which also selects
pulp::standalone-native) when the shipped artifact must not link WebKit,
WebView2, or WebKitGTK. The legacy pulp::view and pulp::standalone targets
remain the compatibility composition for products that instantiate
WebViewPanel. Do not put WebView sources or framework links back onto
pulp-view-core, pulp-view-script, or pulp-format; static-library private
links propagate to the final consumer and silently contaminate native plugins.
Processor's editor hooks (create_view, view_size, on_view_*) are
part of the node ABI surface. When adding a new view lifecycle hook, append
the virtual at the tail of Processor; never insert, remove, reorder, or
re-signature existing virtuals. tools/scripts/node_abi_gate.py --mode=report
is the fast check before pushing. The same rule applies to non-view Processor
virtuals: additive callbacks such as process_f64(...) belong after the
existing f32 process surface, and descriptor fields added for new capabilities
should be appended when positional aggregate initializer compatibility matters.
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 · 2,305 lines · 46 tokens per session scan C 80b9f7ef640b
view-bridge is a skill published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 32,799 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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…
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…