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 alebgl77/claude-inc --skill crogit clone --depth 1 https://github.com/alebgl77/claude-incWrote 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/alebgl77/claude-inc/cro)<a href="https://agentmods.dev/skills/alebgl77/claude-inc/cro"><img src="https://agentmods.dev/badge/skills/alebgl77/claude-inc/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/alebgl77/claude-inc/cro"><img src="https://agentmods.dev/badge/skills/alebgl77/claude-inc/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.00099 | $0.01022 |
| Opus 5.5 | $0.00040 | $0.00409 |
| Sonnet 5.5 | $0.00020 | $0.00204 |
| Haiku 4.5 | $0.00010 | $0.00102 |
Grade A, and why
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRO — Conversion Lead
"Lift conversion rates"
When to use
- A page or funnel underperforms — "the trial page converts at 1.8%, find out why"
- Prioritizing experiments — "we can run 3 tests this quarter, which ones?"
- Pre-launch conversion review — "sanity-check this pricing page before we ship"
- Post-change regression — "signups dropped 20% after the redesign"
- Not for writing the new copy itself — findings hand off to
copywriting
Workflow
- Collect the funnel. Page URL/HTML/screenshots, current conversion rate, traffic sources, and the exact conversion event. No baseline number? Ask for the best estimate and mark the audit directional.
- Walk the friction log. Top to bottom, section by section, log every issue under four labels:
- Clarity — can a first-time visitor say what this is and who it's for within 5 seconds?
- Anxiety — unanswered risk: price surprises, data use, "what happens after I click?"
- Distraction — competing links, carousels, anything pulling from the one intended action
- Motivation — generic value prop, benefits stated as features, no reason to act now
- Run the heuristics.
- Message match — does the headline repeat the promise of the ad or link that brought the click?
- Above-the-fold value prop — headline + benefit + CTA visible without scrolling?
- Form cost — field count × sensitivity; every field must earn its place
- Write the hypothesis backlog. One per finding: "Because we observed [evidence], changing [element] to [variant] will improve [metric]."
- Score ICE. Impact, Confidence, Ease — each 1-10 with a one-line justification. Rank by the product.
- Design the top 3 tests. Control vs variant spec, one primary metric, one guardrail metric, and a minimum-sample note: rough visitors per arm at the current baseline for a realistic lift. Flag tests that traffic volume would stretch past a month.
- Deliver the report in the format below and name the single first test to launch.
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 · 78 lines · 99 tokens per session scan A 02bc12e4f3b2
cro is a skill published in the GitHub repository alebgl77/claude-inc (19 stars, last pushed 5d ago), licensed MIT. It adds 99 tokens to every session and 1,022 once invoked, about $0.0004 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-30.
Other skills, from other repositories
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers hosted cloud browsers for AI agents: the browser-use Python library (Browser(usecloud=True)), Playwright, Puppeteer or any CDP client.
mantis-configure
Configures and validates Mantis pipeline environments, sandbox mechanisms, and AI models. Use to set up workflow.json, auto-detect host capabilities, switch between sandboxes (static-only, gvisor, microsandbox, gce), select AI models, and run fast 1-2s preflight tests. Don't use for scanning source code or running…
meeting-notes
Estructura y formatea notas de reunión siguiendo las mejores prácticas de PM. Úsalo cuando te pidan crear notas de reunión, formatear notas de discusión, capturar elementos de acción, o documentar decisiones de cualquier tipo de reunión. Produce notas estructuradas con decisiones, elementos de acción (responsable +…
technical-debt-register
Documenta y prioriza un backlog de deuda técnica con impacto empresarial, estimaciones de esfuerzo y estrategia de resolución. Úsalo cuando se te pida auditar deuda técnica, crear un registro de deuda, priorizar deuda técnica para un trimestre, documentar atajos arquitectónicos o construir una hoja de ruta de…
cs-health-scorecard
Construir un cuadro de mando de salud del cliente para una cuenta específica. Úsalo cuando te pidan calificar la salud de la cuenta, evaluar el riesgo de renovación, construir un panel de salud o evaluar la probabilidad de que una cuenta se renueve o expanda. Produce un cuadro de mando de salud estructurado con estado…
incident-postmortem
Escribe un postmortem de incidente estructurado o revisión post-incidente. Úsalo cuando se te pida escribir un postmortem, reporte de incidente, revisión P1/P2, reporte de apagón o RCA (análisis de causa raíz). Produce un postmortem sin culpables con cronología, causa raíz, factores contribuyentes, resumen de impacto…