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/codeinfinity1/stram/web-artifact-buildernpx skills add CodeInfinity1/Stram --skill web-artifact-buildergit clone --depth 1 https://github.com/CodeInfinity1/StramWhat 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.00028 | $0.00365 |
| Opus 5 | $0.00014 | $0.00182 |
| Sonnet 5 | $0.00006 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
web-artifact-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 2d 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.
What it actually says
Web Artifact Builder
Purpose
Create local web artifacts that users can open, inspect, and interact with. Artifacts should be complete enough to demonstrate the idea, not static filler.
When To Use
Use for one-off HTML prototypes, demos, interactive visualizations, mini tools, and shareable local artifacts.
Inputs And Evidence
- Desired experience, content, assets, constraints, output path, and target browser.
- Existing files or design references.
Tool Map
write_noteread_filesearch_workspacebrowser_live_openbrowser_live_observebrowser_live_screenshotcanvas_a2ui_create
Workflow
- Define the artifact purpose and first-screen experience.
- Choose a minimal local structure.
- Build with repo/native assets and code.
- Avoid external dependencies unless approved.
- Open and verify in a browser.
- Report output path and interaction status.
Native Implementation Boundaries
- Build project-owned files.
- Do not import Anthropic web-artifact-builder code.
- Do not depend on upstream artifact templates as runtime code.
Safety And Approval
- Avoid remote scripts that can leak data.
- Keep generated assets inside allowed paths.
- Do not overwrite user files without confirmation.
Verification
- Browser observation/screenshot proves rendering.
- Validate links and controls.
- Note if an artifact is static or interactive.
Failure Modes
- Delivering code without testing it.
- Using generic decorative visuals.
- Broken local asset paths.
References
- Shortlist item:
web-artifact-builder.
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.
- 2d ago First seen · 67 lines · 28 tokens per session scan A b90b0ebb63df
web-artifact-builder is a skill published in the GitHub repository CodeInfinity1/Stram (10 stars, last pushed 22d ago), licensed MIT. It adds 28 tokens to every session and 365 once invoked, about $0.0001 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-31.
Other skills, from other repositories
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
opencli-usage
Use at the start of any OpenCLI session — this is the top-level map of what opencli can do, how to discover adapters, what flags and output formats are universal, and which specialized skill to load next. Point here when an agent asks "what can opencli do?" or "how do I find the right command?".
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
smart-search
基于 opencli 命令的智能搜索路由器。当用户想要使用 OpenCLI、CLI 或 API 搜索、查询、查找或研究信息时，尤其是涉及指定网站、社交媒体、技术资料、新闻、购物、旅游、求职、金融或中文内容时，务必使用此 skill.
opencli-browser-sitemap
Use when driving a website with opencli browser and sitemap context is available, requested, or needed to avoid blind navigation. Guides agents to consume site sitemap files lazily, choose adapter/browser fallback paths, resume from state signatures, and mark stale sitemap entries without trusting them over live…