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 form-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/form-cro)<a href="https://agentmods.dev/skills/rajitsaha/100xprism/form-cro"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/form-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/form-cro"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/form-cro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 40 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.00084 | $0.02155 |
| Opus 5.5 | $0.00034 | $0.00862 |
| Sonnet 5.5 | $0.00017 | $0.00431 |
| Haiku 4.5 | $0.00008 | $0.00215 |
Grade A, and why
form-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 1mo 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Form CRO
Maximize form completion rates while capturing the data that matters.
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.
Before recommending, identify:
- Form Type — lead capture (gated content, newsletter), contact, demo/sales request, application, survey/feedback, checkout, quote request
- Current State — field count, current completion rate, mobile vs. desktop split, where users abandon
- Business Context — what happens with submissions, which fields are actually used in follow-up, compliance/legal requirements
Core Principles
1. Every Field Has a Cost
Each field reduces completion. Rule of thumb: 3 fields = baseline; 4-6 fields = 10-25% reduction; 7+ fields = 25-50%+ reduction. For each field ask: Is it absolutely necessary before we can help them? Can we get it another way? Can we ask later?
2. Value Must Exceed Effort
Clear value proposition above the form; make what they get obvious; reduce perceived effort (field count, labels).
3. Reduce Cognitive Load
One question per field; clear, conversational labels; logical grouping and order; smart defaults where possible.
Field-by-Field Optimization
Single field, no confirmation; inline validation; typo detection (did you mean gmail.com?); proper mobile keyboard.
Name
Test single "Name" vs. First/Last — single field reduces friction; split only if personalization requires it.
Phone Number
Make optional if possible; if required, explain why; auto-format as they type; handle country codes.
Company/Organization
Auto-suggest for faster entry; enrich after submission (Clearbit, etc.); consider inferring from email domain.
Job Title/Role
Dropdown if categories matter; free text if wide variation; consider making optional.
Message/Comments (Free Text)
Optional; reasonable character guidance; expand on focus.
What ships with it
2 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.
- 1mo ago First seen · 245 lines · 84 tokens per session scan A b89f989b6dab
form-cro is a skill published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 2,155 once invoked, about $0.0003 per session on Opus 5.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
buywhere-product-catalog
Use BuyWhere's MCP and API surfaces to add product search, price comparison, and deal discovery to AI shopping agents.
billing-automation
Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recu...
ordercli
Check past food delivery orders and track active order status via the ordercli CLI. Supports Foodora with history, reorder, and session management.
stripe-integration
Stripe payment integration. Checkout, subscriptions, webhooks, and billing management. Use when implementing payments or monetization in applications.
pricing-strategy
SaaS pricing models, freemium strategies, tier design, and competitive pricing. Use when designing pricing pages or monetization strategies.
apify-ecommerce
Extract product data, prices, reviews, and seller information from any e-commerce platform using Apify's E-commerce Scraping Tool.