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 rajitsaha/100xprism --skill page-crogit clone --depth 1 https://github.com/rajitsaha/100xprismWrote 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/rajitsaha/100xprism/page-cro)<a href="https://agentmods.dev/skills/rajitsaha/100xprism/page-cro"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/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/rajitsaha/100xprism/page-cro"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/page-cro.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00094 | $0.01092 |
| Opus 5 | $0.00047 | $0.00546 |
| Sonnet 5 | $0.00019 | $0.00218 |
| Haiku 4.5 | $0.00009 | $0.00109 |
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 10d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Page Conversion Rate Optimization (CRO)
Analyze marketing pages and deliver actionable recommendations to improve conversion rates.
Initial Assessment
Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.
Identify first:
- Page Type: homepage, landing page, pricing, feature, blog, about, other
- Primary Conversion Goal: sign up, request demo, purchase, subscribe, download, contact sales
- Traffic Context: where are visitors coming from? (organic, paid, email, social)
CRO Analysis Framework
Analyze these dimensions, in order of impact:
1. Value Proposition Clarity (Highest Impact)
Can a visitor grasp what this is and why they should care within 5 seconds? Is the primary benefit clear, specific, differentiated, and in customer language (not company jargon)?
Common issues: feature-focused instead of benefit-focused; too vague or too clever (sacrificing clarity); saying everything instead of the most important thing.
2. Headline Effectiveness
Does it communicate the core value proposition? Specific enough to be meaningful? Does it match the traffic source's messaging?
Strong patterns:
- Outcome-focused: "Get [desired outcome] without [pain point]"
- Specificity: numbers, timeframes, concrete details
- Social proof: "Join 10,000+ teams who..."
3. CTA Placement, Copy, and Hierarchy
One clear primary action, visible without scrolling, with button copy that communicates value, not just action:
- Weak: "Submit," "Sign Up," "Learn More"
- Strong: "Start Free Trial," "Get My Report," "See Pricing"
Hierarchy: logical primary vs. secondary CTA structure; CTAs repeated at key decision points.
4. Visual Hierarchy and Scannability
Can someone scanning get the main message? Are the most important elements visually prominent? Enough white space? Do images support or distract from the message?
What ships with it
3 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.
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.
- 10d ago First seen · 121 lines · 94 tokens per session scan A 76a04afc1f5b
page-cro is a skill published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 10d ago), licensed MIT. It adds 94 tokens to every session and 1,092 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
ad-campaign-analyzer
Analyze cross-channel campaign data, quantify uncertainty, and propose evidence-labeled budget tests without overstating causality.
google-analytics
Skill "google-analytics" from VKirill/claude-lane-stack, covering version requirements (may 2026), usage, use this skill when, do not use this skill when and purpose.
google-tag-manager
Skill "google-tag-manager" from VKirill/claude-lane-stack, covering 🎯 version requirements (june 2026), usage, use this skill when, do not use this skill when and purpose.
analyzing-windows-lnk-files-for-artifacts
Parse Windows LNK shortcut files to extract target paths, timestamps, volume information, and machine identifiers for forensic timeline reconstruction.
analyzing-memory-forensics-with-lime-and-volatility
Performs Linux memory acquisition using LiME (Linux Memory Extractor) kernel module and analysis with Volatility 3 framework. Extracts process lists, network connections, bash history, loaded kernel modules, and injected code from Linux memory images. Use when performing incident response on compromised Linux systems.
laravel-api
Build production-ready RESTful APIs with Laravel. Covers authentication (Sanctum/Passport), versioning, resources, rate limiting, and API testing.