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 MoizIbnYousaf/marketing-cli --skill conversion-flow-crogit clone --depth 1 https://github.com/MoizIbnYousaf/marketing-cliWrote 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/moizibnyousaf/marketing-cli/conversion-flow-cro)<a href="https://agentmods.dev/skills/moizibnyousaf/marketing-cli/conversion-flow-cro"><img src="https://agentmods.dev/badge/skills/moizibnyousaf/marketing-cli/conversion-flow-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/moizibnyousaf/marketing-cli/conversion-flow-cro"><img src="https://agentmods.dev/badge/skills/moizibnyousaf/marketing-cli/conversion-flow-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.00178 | $0.02471 |
| Opus 5.5 | $0.00071 | $0.00988 |
| Sonnet 5.5 | $0.00036 | $0.00494 |
| Haiku 4.5 | $0.00018 | $0.00247 |
Grade A, and why
conversion-flow-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 2mo 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conversion Flow CRO
Purpose
Audit and optimize any multi-step conversion flow — signup, onboarding, trial-to-paid, checkout, upgrade. Map every step, find where people drop off, and fix each screen with specific copy and UX changes.
Reads
brand/audience.md— Personas, pain points, motivation levels at each stagebrand/positioning.md— Value props for reinforcement copy at each stepbrand/voice-profile.md— Brand voice for all copy suggestions
Brand Integration
- audience.md — Persona determines friction tolerance. A developer persona accepts more setup steps; a non-technical buyer needs fewer. Pain points inform which value reminders to show at each step.
- positioning.md — Value proposition reinforcement copy at each step should echo the positioning angle. If the brand positions on "saves time," every motivation booster references time savings.
- voice-profile.md — All redesigned copy (headlines, CTAs, supporting text) must match brand voice. A casual brand writes "Almost there!" while a professional brand writes "One final step."
Workflow
Step 1: Map the Current Flow
Get the flow information. Try these in order:
- User provides screenshots or screen recordings — Best source, map directly
- Read the codebase — If accessible, find route files, page components, and form definitions
- User walks through the flow verbally — Accept but flag that recommendations will be more accurate with actual screens
- Use browser tool on live URL — Walk through the flow step by step
If the flow is partially provided (only some screens), audit what's available and note which steps need investigation.
Document every screen/step in the flow:
Flow: [Signup / Onboarding / Upgrade / Checkout]
Step 1: [Page/Screen name]
- URL/Route: [path]
- Fields/Actions: [what user must do]
- Copy: [headline, body, CTA]
- Friction points: [identified issues]
Step 2: [Next screen]
...
Total steps: [N]
Total required fields: [N]
Total decisions: [N]
Estimated completion time: [X minutes]
What ships with it
1 file 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.
- 2mo ago First seen · 250 lines · 178 tokens per session scan A bf18b6b09454
conversion-flow-cro is a skill published in the GitHub repository MoizIbnYousaf/marketing-cli (32 stars, last pushed 10d ago), licensed MIT. It adds 178 tokens to every session and 2,471 once invoked, about $0.0007 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
principle-experience-first
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
principle-redesign-from-first-principles
Apply when integrating a new requirement into an existing design.
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
hooked-ux
Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "habit formation", "engagement loops", "habit zone", or "the manipulation matrix". Also trigger when designing notification or re-engagement strategies, building…
web-typography
Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", "typographic scale", or "the text is hard to read". Also trigger when choosing between system…
product-enrich
Enrich FF&E schedule rows with categories, colors, materials, and style tags. Use to tag, categorize, or fill those missing fields; not to research new products.