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 Ertinox7711/SGRR-AGI-V2 --skill market-landinggit clone --depth 1 https://github.com/Ertinox7711/SGRR-AGI-V2Wrote 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/ertinox7711/sgrr-agi-v2/market-landing)<a href="https://agentmods.dev/skills/ertinox7711/sgrr-agi-v2/market-landing"><img src="https://agentmods.dev/badge/skills/ertinox7711/sgrr-agi-v2/market-landing/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/ertinox7711/sgrr-agi-v2/market-landing"><img src="https://agentmods.dev/badge/skills/ertinox7711/sgrr-agi-v2/market-landing.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.00053 | $0.03193 |
| Opus 5 | $0.00026 | $0.01597 |
| Sonnet 5 | $0.00011 | $0.00639 |
| Haiku 4.5 | $0.00005 | $0.00319 |
Grade A, and why
market-landing 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 3d 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
97% identical to market-landing — 5 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing Page CRO Analysis
Skill Purpose
Perform a comprehensive Conversion Rate Optimization (CRO) analysis on any landing page. This skill produces a section-by-section teardown with prioritized, actionable fixes that directly impact conversion rates.
When to Use
- User provides a landing page URL and asks for conversion optimization
- User asks for landing page feedback, review, or audit
- User wants to improve signup, lead capture, or purchase rates
- Triggered by
/market landing <url>or/market cro <url>
How to Execute
Step 1: Identify the Page Type
Determine which type of landing page you are analyzing. This affects benchmark expectations and scoring weights.
| Page Type | Primary Goal | Good CR | Great CR |
|---|---|---|---|
| Lead Capture | Email/form submission | 5-10% | 15%+ |
| SaaS Signup | Free trial or freemium signup | 3-7% | 10%+ |
| E-commerce Product | Add to cart / Purchase | 2-4% | 5%+ |
| Webinar Registration | Register for event | 20-30% | 40%+ |
| App Download | Install app | 10-15% | 20%+ |
| Waitlist | Join waitlist | 15-25% | 35%+ |
| Consultation Booking | Schedule a call | 5-10% | 15%+ |
| Nonprofit Donation | Make a donation | 2-5% | 8%+ |
Step 2: Run the 7-Point CRO Framework
Analyze each section in order. Score each section 1-10 and provide specific findings.
Section 1: Hero Section (Weight: 25%)
The first screen a visitor sees. This is where 80% of conversion decisions begin.
Checklist:
- Headline is visible within 2 seconds of page load
- Headline communicates the primary benefit (not a feature)
- Headline is under 10 words
- Subheadline expands on the headline with specificity
- Primary CTA is above the fold
- CTA button color contrasts with the background
- CTA text is action-oriented (not "Submit" or "Click Here")
- Hero image or video supports the message (not generic stock)
- Trust badges or social proof visible above the fold
- Page loads in under 3 seconds
- No navigation menu competing with the CTA (for dedicated landing pages)
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.
- 3d ago First seen · 334 lines · 0 tokens per session scan A 80875bdc665b
market-landing is a skill published in the GitHub repository Ertinox7711/SGRR-AGI-V2 (1 stars, last pushed 4d ago), licensed MIT. It adds 53 tokens to every session and 3,193 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to market-landing, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.
retrospective-audit
Stage B of /prflow:retrospective-weekly: given a most-recent-first subset of one recurring pattern's occurrence-PR context bundles (bounded by auditbundlecap), re-derive the root cause and return one JSON object carrying a ranked findings array (one to three sub-patterns) — no edits, no worktree. Invoked as a subagent…
docs
Use when documentation generally needs to catch up with a branch before pushing or merging, covering internal developer docs, external customer-facing docs, and release notes together — "update the docs", "do a docs pass before I merge", "make sure everything's documented". Prefer this when no single documentation…
tmux-lane-orchestrator
Manage one tmux agent lane from its matching ops pane, inspect live pane state and Codex logs on cold start, and produce concise manager summaries for OpenClaw and adjacent project work.