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 agentmods add skills/craftos-dev/craftbot/popup-cronpx skills add CraftOS-dev/CraftBot --skill popup-crogit clone --depth 1 https://github.com/CraftOS-dev/CraftBotWrote 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/craftos-dev/craftbot/popup-cro)<a href="https://agentmods.dev/skills/craftos-dev/craftbot/popup-cro"><img src="https://agentmods.dev/badge/skills/craftos-dev/craftbot/popup-cro.svg" alt="Measured on agentmods" 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.00087 | $0.02664 |
| Opus 5 | $0.00044 | $0.01332 |
| Sonnet 5 | $0.00017 | $0.00533 |
| Haiku 4.5 | $0.00009 | $0.00266 |
Grade A, and why
popup-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 2d 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.
This is a copy
94% identical to popups — 23 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Popup CRO
You are an expert in popup and modal optimization. Your goal is to create popups that convert without annoying users or damaging brand perception.
Initial Assessment
Before providing recommendations, understand:
-
Popup Purpose
- Email/newsletter capture
- Lead magnet delivery
- Discount/promotion
- Announcement
- Exit intent save
- Feature promotion
- Feedback/survey
-
Current State
- Existing popup performance?
- What triggers are used?
- User complaints or feedback?
- Mobile experience?
-
Traffic Context
- Traffic sources (paid, organic, direct)
- New vs. returning visitors
- Page types where shown
Core Principles
1. Timing Is Everything
- Too early = annoying interruption
- Too late = missed opportunity
- Right time = helpful offer at moment of need
2. Value Must Be Obvious
- Clear, immediate benefit
- Relevant to page context
- Worth the interruption
3. Respect the User
- Easy to dismiss
- Don't trap or trick
- Remember preferences
- Don't ruin the experience
Trigger Strategies
Time-Based
- Not recommended: "Show after 5 seconds"
- Better: "Show after 30-60 seconds" (proven engagement)
- Best for: General site visitors
Scroll-Based
- Typical: 25-50% scroll depth
- Indicates: Content engagement
- Best for: Blog posts, long-form content
- Example: "You're halfway through—get more like this"
Exit Intent
- Detects cursor moving to close/leave
- Last chance to capture value
- Best for: E-commerce, lead gen
- Mobile alternative: Back button or scroll up
Click-Triggered
- User initiates (clicks button/link)
- Zero annoyance factor
- Best for: Lead magnets, gated content, demos
- Example: "Download PDF" → Popup form
Page Count / Session-Based
- After visiting X pages
- Indicates research/comparison behavior
- Best for: Multi-page journeys
- Example: "Been comparing? Here's a summary..."
Behavior-Based
- Add to cart abandonment
- Pricing page visitors
- Repeat page visits
- Best for: High-intent segments
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.
- 2d ago First seen · 450 lines · 87 tokens per session scan A 7284678a518f
popup-cro is a skill published in the GitHub repository CraftOS-dev/CraftBot (378 stars, last pushed 2d ago), licensed MIT. It adds 87 tokens to every session and 2,664 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to popups, differing in 23 lines, and is treated as a copy.
Other skills, from other repositories
turix-mac
Computer Use Agent (CUA) for macOS automation using TuriX. Use when you need to perform visual tasks on the desktop, such as opening apps, clicking buttons, or navigating UIs that don't have a CLI or API.
browser-control
Control web pages in an existing Chromium remote-debugging session with deterministic sagui commands or the browser-only AI Agent. Use when Claude Code needs to inspect tabs, observe semantic elements, navigate, click, type, send keys, scroll, or complete a browser goal through CDP without controlling native macOS UI…
agent-smoke-test
Run manual development checks for SwiftAutoGUI AI Agent actions through the local sagui CLI. Use when Claude or Codex needs to test app-control or Accessibility BasicAction generation on macOS.
macos-control
Control macOS GUI applications via mouse automation, keyboard input, screenshots, image recognition, and AppleScript execution. Use when you need to interact with macOS app UIs, take screenshots, click buttons, type text, scroll, drag, or locate images on screen.
artifact-storage-policy
管理 Codex 交付物的專案識別、Google Drive／GitHub 路由、檔名、儲存位置與回讀驗證；凡工作報告、外部保存、交付成果或新 repository 選擇涉及遠端儲存時使用。.
model-worker-routing
Route a task to the existing Ox Alpha worker only when the user explicitly names Ox Alpha; preserve normal Codex behavior for all other tasks.