Prismer Cloud is an infrastructure layer for AI agents that provides shared learning, compressed context, persistent memory, collaboration, messaging, tasks, identity, and workspaces. It is for agents and the people building or using long-running agent systems that need information and outcomes to persist across sessions. The catalogue entries provide skills, hooks, agents, instructions, and a plugin for using Prismer Cloud.
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 skills add Prismer-AI/PrismerCloud --skill web-artifacts-buildergit clone --depth 1 https://github.com/Prismer-AI/PrismerCloudWrote 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/prismer-ai/prismercloud/web-artifacts-builder)<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/web-artifacts-builder"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/web-artifacts-builder/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/prismer-ai/prismercloud/web-artifacts-builder"><img src="https://agentmods.dev/badge/skills/prismer-ai/prismercloud/web-artifacts-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.01079 |
| Opus 5.5 | $0.00025 | $0.00432 |
| Sonnet 5.5 | $0.00013 | $0.00216 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
web-artifacts-builder 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 21d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delivering the bundled artifact
When the bundle script (scripts/bundle-artifact.sh) produces the
single-file HTML artifact, deliver that bundle.html with cloud deliver <abs-path> — this is the one command for a final artifact: it attaches the
file to your current reply. Run cloud deliver once per output file. See the
office-artifacts delivery contract for the full rules (incl. the hermes
--run-id / --conversation-id flags).
Do NOT also run cloud file send on the same bundle — that posts a separate
file-only message, delivering it twice. cloud file send is only for ad-hoc
mid-conversation sharing, never for your final deliverable. And cloud file upload is NOT a delivery command (it only uploads bytes and returns an
uploadId — nothing reaches the user) — always use cloud deliver.
Do NOT hand-build POST /api/im/assets calls or assemble ContentBlock JSON
yourself, and do NOT paste the HTML source into the reply body — large
bundles burn tokens on every downstream turn, and the delivery command
registers the asset so the chat renderer can offer a preview/open button.
Web Artifacts Builder
To build powerful frontend Prismer artifacts, follow these steps:
- Initialize the frontend repo using
scripts/init-artifact.sh - Develop your artifact by editing the generated code
- Bundle all code into a single HTML file using
scripts/bundle-artifact.sh - Display artifact to user
- (Optional) Test the artifact
Stack: React 18 + TypeScript + Vite + Parcel (bundling) + Tailwind CSS + shadcn/ui
Runtime baseline (release 201)
The Prismer sandbox image bakes pnpm@9 and Node 20+, so scripts/init-artifact.sh
will skip the "install pnpm" branch and proceed directly to the workspace
create + dependency install. If pnpm is genuinely missing (non-sandbox env),
fail the task with a clear "sandbox image missing pnpm — rebuild required"
message rather than installing it on the fly: agent-time npm install -g
contaminates the per-task workdir and slows every dispatch.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 21d ago Changed · +1 lines · -1 tokens per session bb7f74d88ace
- 1mo ago First seen · 104 lines · 64 tokens per session scan A ac1d2d437ea3
web-artifacts-builder is a skill published in the GitHub repository Prismer-AI/PrismerCloud (1,384 stars, last pushed 6d ago), licensed MIT. It adds 63 tokens to every session and 1,079 once invoked, about $0.0003 per session on Opus 5.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
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
ambience-skill
Layer A ambience-and-typographic-motion reference anchored to the react-bits catalog (reactbits.dev). Stacks on any style skill whenever work adds a hero atmosphere, an animated or shader background, a typographic reveal (split, blur, shimmer, typewriter, count-up, marquee), scroll storytelling, or card surface…
21st-ui
Find, install, and generate UI with 21st.dev. Use when the user asks for a UI component (pricing table, hero, navbar, dashboard, form, etc.), wants design inspiration, needs a brand logo as an SVG component, or wants to generate new UI from a prompt.
cometchat-react-v7-customization
Theme and brand the React v7 UI Kit — light/dark mode, CSS custom-property design tokens, per-component style overrides. Triggers: 'change chat colors', 'dark mode chat', 'match my brand', 'customize cometchat theme', 'override message list styles'.
shadcn
Current best-practices guide for shadcn/ui applications. Before applying primitive-specific guidance, inspect whether the checked-in components use Radix UI or Base UI; current shadcn supports both (Base UI is the default for new projects) and their composition APIs differ. Component installs and upgrades go through…