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 ucoz-skills/agent-skills --skill ucoz-provisioning-skillgit clone --depth 1 https://github.com/ucoz-skills/agent-skillsWrote 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/ucoz-skills/agent-skills/ucoz-provisioning-skill)<a href="https://agentmods.dev/skills/ucoz-skills/agent-skills/ucoz-provisioning-skill"><img src="https://agentmods.dev/badge/skills/ucoz-skills/agent-skills/ucoz-provisioning-skill/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/ucoz-skills/agent-skills/ucoz-provisioning-skill"><img src="https://agentmods.dev/badge/skills/ucoz-skills/agent-skills/ucoz-provisioning-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 8 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 65 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 73 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 92 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Excessive Agency · line 34 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium MCP Rug Pull · line 91 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 131 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Excessive Agency · line 395 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 399 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00091 | $0.05036 |
| Opus 5 | $0.00046 | $0.02518 |
| Sonnet 5 | $0.00018 | $0.01007 |
| Haiku 4.5 | $0.00009 | $0.00504 |
Grade A, and why
ucoz-provisioning-skill 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 13d 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 — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
uCoz Site Launch and MCP Connection Assistant (uCoz MCP Launch Assistant)
Rule 0 — Usage accounting
After the skill's main work completes successfully, record usage:
skills_tool(action="register_usage", skill_id="ucoz-provisioning-skill")
If the usage API is unavailable or returns an error, show a brief warning and continue the skill's main workflow. Do not ask the user for a UUID, token, or site URL — the site and token come from the active ucoz-mcp connection.
Purpose
This is a portable agent skill for preparing a uCoz site so that any MCP-capable agent can work with it through the official ucoz-mcp server.
The skill is intentionally a provisioning/preparation helper layer, not a content or page layout skill. It finishes when the site is ready, MCP credentials are collected, and the agent can hand the task off to the next task skill.
Runtime Requirements
The provisioning scenario requires an agent environment with browser automation capability, because the agent must interact with the live uCoz web interface: site creation, domain zone discovery, theme/configuration cards, module enablement, uAPI and FTP setup.
Recommended stack:
node >= 18
playwright
Similar browser automation tools also work if they can read the live DOM, click elements, submit forms, and read page state.
The official ucoz-mcp server remains the required MCP execution layer after credentials are prepared. Browser automation is for onboarding/provisioning; MCP is for operations on the connected site.
Mandatory Execution: New Site via Browser
Order without exceptions: first chat dialog (clarify and confirm agreement on each parameter), then write to environment variables and run the runner. Do not silently substitute a preset, address, or arbitrary UCOZ_ORIGIN based on guesswork alone.
What the agent must clarify in chat (new site)
- uCoz account login email (can be provided as plain text — it is not a password secret).
- Account password: the agent does not replay the secret from history unless necessary; then one of two paths — the user sets the password locally in ENV/.env or explicitly passes it to the agent for local write to
.env(without publishing the secret in package files/commits). - New site address: full
prefix.zonestring or prefix and desired zone separately — and confirmation before launch. - Site theme/configuration card is chosen from the live uCoz interface.
browser-runner/preset-catalog.jsonis advisory/fallback only for aliases and debugging. Do not choose "Landing" or any other preset by default; if the user asks for a theme not in the live UI, say so explicitly and ask them to choose from the visible list. - Site name in the modal:
UCOZ_SITE_TITLE, if the prefix alone is not enough. - If needed: non-default
UCOZ_ORIGIN,UCOZ_HEADLESSmode.
What ships with it
21 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.
- browser-runner/.env.example 548 B
- browser-runner/.gitignore 35 B
- browser-runner/package-lock.json 2.2 KB
- browser-runner/package.json 491 B
- browser-runner/preset-catalog.json 3.0 KB
- browser-runner/provision-new-site.mjs 1.2 KB runs code
- browser-runner/ucoz-provision.cjs 36 KB runs code
- examples/existing-site-flow.md 468 B
- examples/new-site-flow.md 827 B
- manifest.json 2.5 KB
- QUICK_START.md 905 B
- README.md 6.7 KB
- references/browser-runner.md 8.4 KB
- references/downstream-skills.md 533 B
- references/NEW_SITE_WORKFLOW.md 1.1 KB
- references/workflow.md 2.8 KB
- templates/claude-desktop-config.json 384 B
- templates/cursor-mcp.json 384 B
- templates/generic-mcp-env.sh 300 B runs code
- templates/generic-system-prompt.md 1.4 KB
- templates/hermes-config.yaml 442 B
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.
- 13d ago First seen · 420 lines · 91 tokens per session scan A 6c2a1272a176
ucoz-provisioning-skill is a skill published in the GitHub repository ucoz-skills/agent-skills (10 stars, last pushed 16d ago), licensed MIT. It adds 91 tokens to every session and 5,036 once invoked, about $0.0005 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
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…