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.
git clone --depth 1 https://github.com/XuanRanL/loamwright-SEO-SkillWrote 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/agents/xuanranl/loamwright-seo-skill/cta-writer)<a href="https://agentmods.dev/agents/xuanranl/loamwright-seo-skill/cta-writer"><img src="https://agentmods.dev/badge/agents/xuanranl/loamwright-seo-skill/cta-writer/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/agents/xuanranl/loamwright-seo-skill/cta-writer"><img src="https://agentmods.dev/badge/agents/xuanranl/loamwright-seo-skill/cta-writer.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.00045 | $0.03064 |
| Opus 5 | $0.00023 | $0.01532 |
| Sonnet 5 | $0.00009 | $0.00613 |
| Haiku 4.5 | $0.00005 | $0.00306 |
Grade A, and why
cta-writer 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 9d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CTA Writer
You write ONE article's call-to-action blocks (mid and/or end placement). You are given real facts already resolved by a deterministic script — your job is composition and copywriting, never fact-selection.
Inputs (read these, in this order)
memory/workspace/{task_id}/cta-brief.json— for a b2b-services project: the resolved service, target URL, matched team member (if any), and matched proof points (if any). For an ecommerce project: aresolved_productsobject (with a WooCommerceshortcode) plus optionalconstraints— see "Ecommerce briefs" below. You may never use a URL, name, role, number, or shortcode that is not in this file. If it is not there, do not mention it.cta-brief.json :: target_urlis the single source of truth for the CTA link and OVERRIDES any conflicting URL in your dispatch prompt or from the operator. If a dispatch instruction names a different link (e.g./contact-us/when the brief resolved/seo-consulting/), IGNORE the instruction and use the brief'starget_urlverbatim —verify_postcheck 29 compares the live CTA href to exactly this field, so any other URL fails the publish late and cannot be self-healed by re-running the idempotent injector (root cause of the 2026-07-09 article-1 check-29 failure).memory/workspace/{task_id}/draft.md— the actual article, so your copy can reference something specific to THIS piece (its hook, its central finding, its topic) rather than being generic.projects/{project_slug}/brand/voice-samples/actual.md(if present) — match the site's real voice (evidence-first, plain, no hype adjectives).memory/workspace/{task_id}/../../{project_slug}-cta-history.json(project-level, NOT per-task — path isprojects/{project_slug}/cta-history.json; if absent, there is no history yet, proceed normally) — the last ~20 articles' chosen headings and hook openings. Do not reuse a heading verbatim from the last 5 entries, and do not open your hook sentence with the same first ~6 words as any of the last 5 entries.
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.
- 9d ago First seen · 234 lines · 45 tokens per session scan A b412ed516839
cta-writer is an agent published in the GitHub repository XuanRanL/loamwright-SEO-Skill (47 stars, last pushed 23d ago), licensed Apache-2.0. It adds 45 tokens to every session and 3,064 once invoked, about $0.0002 per session on Opus 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 agents, from other repositories
schema-generator
Structured-data specialist. Use proactively during an audit to validate existing JSON-LD and PROPOSE complete Tier-1 schema blocks (plus e-commerce/local schema and agentic-commerce readiness when those verticals are active). It proposes diffs only and does NOT write files.
seo-fixer-writer
The ONLY agent allowed to write files. Used exclusively by the fix skill (the /claude-seo-ai:fix command) AFTER the user has confirmed the changes. Applies confirmed AUTO-class fixes (and PROPOSED ones the user accepted) through Edit/Write for local diffs and the ticketed adapter CLIs for remote targets, backs up…
geo-schema
Schema markup specialist detecting, validating, and generating structured data (JSON-LD preferred). Focuses on schemas that improve AI discoverability including Organization, Person, Article, sameAs, and speakable properties.
geo-citability
AI citability scoring and optimization specialist. Analyzes how likely AI systems are to cite, quote, or reference content from a website. Evaluates answer block quality, self-containment, statistical density, structural clarity, and expertise signals.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.