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/webiny/webiny-js/website-buildernpx skills add webiny/webiny-js --skill website-buildergit clone --depth 1 https://github.com/webiny/webiny-jsWrote 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/webiny/webiny-js/website-builder)<a href="https://agentmods.dev/skills/webiny/webiny-js/website-builder"><img src="https://agentmods.dev/badge/skills/webiny/webiny-js/website-builder.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.00019 | $0.03434 |
| Opus 5 | $0.00010 | $0.01717 |
| Sonnet 5 | $0.00004 | $0.00687 |
| Haiku 4.5 | $0.00002 | $0.00343 |
Grade A, and why
webiny-admin-website-builder-catalog 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 419 lines · 19 tokens per session scan A 22d34a42dd3a
webiny-admin-website-builder-catalog is a skill published in the GitHub repository webiny/webiny-js (8,033 stars, last pushed today), with no licence file. It adds 19 tokens to every session and 3,434 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-30.
Other skills, from other repositories
wordclaw-cms
Use when Codex is connected to a WordClaw MCP server or WordClaw-backed REST runtime. Start with system://capabilities, system://deployment-status, system://current-actor, and system://workspace-context, then use guidetask or resolveworkspacetarget before writing. Covers schema-bound authoring, review workflows, asset…
wordclaw-cms
Use when OpenClaw is connected to a WordClaw MCP server or WordClaw-backed REST runtime. Start with system://capabilities, system://deployment-status, system://current-actor, and system://workspace-context, then use guidetask or resolveworkspacetarget before writing. Covers schema-bound authoring, review workflows…
ui4
Manually invoked skill for reskinning Payload UI components. Requires Figma URL. Usage: /ui4.
payload
Use when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
triage-ci-flake
Use when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing tests.
audit-dependencies
Use when fixing dependency vulnerabilities, running pnpm audit, or when the audit-dependencies CI check fails.