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 Humblytics/humblytics-marketing-skills --skill page-crogit clone --depth 1 https://github.com/Humblytics/humblytics-marketing-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/humblytics/humblytics-marketing-skills/page-cro)<a href="https://agentmods.dev/skills/humblytics/humblytics-marketing-skills/page-cro"><img src="https://agentmods.dev/badge/skills/humblytics/humblytics-marketing-skills/page-cro/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/humblytics/humblytics-marketing-skills/page-cro"><img src="https://agentmods.dev/badge/skills/humblytics/humblytics-marketing-skills/page-cro.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.00098 | $0.02478 |
| Opus 5 | $0.00049 | $0.01239 |
| Sonnet 5 | $0.00020 | $0.00496 |
| Haiku 4.5 | $0.00010 | $0.00248 |
Grade A, and why
page-cro 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Page CRO
Purpose
Perform deep conversion audits on individual pages — landing pages, homepages, pricing pages, product pages, signup flows. Identifies specific conversion barriers and delivers actionable recommendations for copy, layout, CTAs, social proof, and user experience improvements.
When to Use
- Auditing a landing page before or after launch
- Reviewing a pricing page for conversion optimization
- Improving a homepage that has high traffic but low conversion
- Optimizing a signup or onboarding flow
- Reviewing a page that has declining conversion rates
- Preparing recommendations before an A/B test
Before You Start
- Get the page URL or content — Either a live URL, screenshot, or the page code/copy
- Understand the page goal — What is the single most important action a visitor should take?
- Know the audience — Who lands on this page? What brought them here?
- Current performance — If available, get conversion rate, bounce rate, time on page, scroll depth from Humblytics
- Traffic sources — Where does traffic come from? This affects messaging expectations.
- Look for context — Check project docs for brand, product, and competitive positioning
The Page CRO Audit Framework
1. First Impression (0-5 seconds)
The most critical window. Within 5 seconds, a visitor decides to stay or leave.
Check:
- Is the headline clear and specific? Does it communicate the value proposition in under 10 words?
- Does the subheadline explain what the product does and for whom?
- Is the CTA visible above the fold without scrolling?
- Is there visual hierarchy? Does the eye know where to go?
- Does the page match the traffic source? (Ad copy -> landing page message match)
- Is the page loading fast? (>3 seconds kills conversion)
Common issues:
- Headline is clever instead of clear
- No CTA above the fold
- Too many competing elements
- Stock photography that says nothing
- Message mismatch with the ad or link that brought them here
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 · 237 lines · 98 tokens per session scan A 684772892446
page-cro is a skill published in the GitHub repository Humblytics/humblytics-marketing-skills (84 stars, last pushed 8d ago), licensed MIT. It adds 98 tokens to every session and 2,478 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-30.
Other skills, from other repositories
ab-test-generator
Generate A/B test variants for affiliate content. Triggers on: "create A/B test", "test my headline", "optimize my CTA", "generate variants", "split test ideas", "improve click-through rate", "test my landing page copy", "headline alternatives", "CTA variations", "which version is better", "optimize conversions"…
authoring-ci-workflows
Use when adding or editing a GitHub Actions workflow, composite action, or reusable workflow under .github/ — new CI jobs, triggers, matrices, checkout/clone tuning, action pinning, GitHub App token auth, concurrency groups, timeout-minutes, paths filters, caching, or runner choice. Covers PostHog's workflow-authoring…
isolating-product-facade-contracts
Plan and execute product isolation migrations to a facade plus contract layer in PostHog, following the Visual review architecture. Use when a product still exposes internals (models/logic/views) across boundaries and needs migration toward contracts.py + facade/api.py + presentation separation, with a PR strategy…
triaging-merge-queue-failures
Decision procedure for a PR that failed or was removed from the Trunk merge queue: classify the kick (superseded by a newer commit, not mergeable, a gate that failed on a cancelled run, real failure, one-off flake, or repo-wide flaky/infra issue) and take the matching action (wait, hold and fix, requeue once, or…
debugging-mcp-analytics
Debug, support, and build PostHog MCP Analytics — product analytics for MCP servers (the @posthog/mcp and posthog.mcp SDKs plus the mcpanalytics product). Use when MCP analytics data looks wrong or missing ("events aren't showing", "intent clusters are empty", "sessions are missing", "per-tool numbers look wrong")…
debugging-ci-failures
Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?"). Use when the user asks why CI is red, asks for the current CI or master status, or mentions a failing check, GitHub Actions run…