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-ad-campaign-landing-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-ad-campaign-landing-skill)<a href="https://agentmods.dev/skills/ucoz-skills/agent-skills/ucoz-ad-campaign-landing-skill"><img src="https://agentmods.dev/badge/skills/ucoz-skills/agent-skills/ucoz-ad-campaign-landing-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-ad-campaign-landing-skill"><img src="https://agentmods.dev/badge/skills/ucoz-skills/agent-skills/ucoz-ad-campaign-landing-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 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 11 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 33 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 94 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.00059 | $0.01988 |
| Opus 5 | $0.00030 | $0.00994 |
| Sonnet 5 | $0.00012 | $0.00398 |
| Haiku 4.5 | $0.00006 | $0.00199 |
Grade A, and why
ucoz-ad-campaign-landing-skill scanned grade A 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Version 1: agent performs all operations natively — without Python scripts. Publishing via MCP (`templates_tool`, `ftp_tool`), API requests via Shell (`curl`), HTML and JSON generated by the agent. How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ad Campaign Landing Skill (agent-native)
One skill = from ad creative → segment landing (hyper-segmentation) + UTM package + push to Yandex Direct / Google Ads via API.
Version 1: agent performs all operations natively — without Python scripts. Publishing via MCP (templates_tool, ftp_tool), API requests via Shell (curl), HTML and JSON generated by the agent.
Rule 0 — Usage accounting
After the skill's main work completes successfully, record usage:
skills_tool(action="register_usage", skill_id="ucoz-ad-campaign-landing-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.
Main scenario (creative → landing)
references/PIPELINE.md §2A — ad exists → headline_1 = H1 → separate URL → page_add.
ad (CSV or text)
→ agent builds segments.json (headline_1 = H1, page_ownurl = transliteration)
→ agent checks message match (COPY.md §Message Match)
→ agent generates HTML per LANDING_PLAYBOOK.md rules
→ LANDING_PLAYBOOK.md (page_add, §0.1)
→ agent builds UTM strings
→ (optional) push to Yandex Direct/Google Ads — only with user permission
→ OUTPUT.md
No creative → Wordstat/WebSearch: references/PIPELINE.md §2B (branch 2B).
Start with user
No full brief → references/INTAKE.md → brief.json → pipeline.
Must clarify with user (if not stated), before API push and large-scale deployment:
| Question | Brief field | Impact |
|---|---|---|
| Test or full Yandex Direct API access? | yandex_direct_access |
sandbox vs prod host |
| One landing or separate URL per ad/segment? | landing_scale, max_segments |
number of page_add, message match |
Branching and checklist: INTAKE.md (§ API access, § Landing scale).
What ships with it
16 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.
- .env.example 3.0 KB
- .gitignore 16 B
- references/ADS.md 5.6 KB
- references/COPY.md 5.5 KB
- references/DIRECT_API.md 11 KB
- references/EXAMPLE.md 4.5 KB
- references/GOOGLE_ADS.md 5.2 KB
- references/INTAKE.md 12 KB
- references/LANDING_PLAYBOOK.md 30 KB
- references/OUTPUT.md 3.3 KB
- references/PIPELINE.md 5.0 KB
- references/RESEARCH.md 5.1 KB
- templates/ads.example.csv 318 B
- templates/ads.multi.example.csv 737 B
- templates/brief.example.json 761 B
- templates/segments.manifest.example.json 2.0 KB
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.
- 12d ago First seen · 176 lines · 59 tokens per session scan A c2036818e294
ucoz-ad-campaign-landing-skill is a skill published in the GitHub repository ucoz-skills/agent-skills (10 stars, last pushed 16d ago), licensed MIT. It adds 59 tokens to every session and 1,988 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…