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 seo-machinegit 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/seo-machine)<a href="https://agentmods.dev/skills/moizibnyousaf/marketing-cli/seo-machine"><img src="https://agentmods.dev/badge/skills/moizibnyousaf/marketing-cli/seo-machine.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.00216 | $0.05086 |
| Opus 5 | $0.00108 | $0.02543 |
| Sonnet 5 | $0.00043 | $0.01017 |
| Haiku 4.5 | $0.00022 | $0.00509 |
Grade C, and why
seo-machine scanned grade C with 1 finding 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 4d 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
| 3 | Research backend resolved (`skills/openseo/references/backend-contract.md`) | Never refuse to run — fall through to manual mode. | 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.
SEO Machine
End-to-end engine for building organic search traffic. Ships dozens of programmatic landing pages — alternatives, comparisons, use-cases, playbooks — backed by real keyword research, with a persistent roadmap the user resumes across sessions.
Conversion-first (alternatives + comparisons before blogs). Publish-early (a thin page indexed today beats a perfect page indexed in three weeks). Stack-native (writes into the user's framework — Next.js, Astro, Rails+Inertia, or a portable markdown fallback).
Two modes, auto-detected
| Mode | When | What it produces |
|---|---|---|
| Initialize | docs/seo-machine.md does not exist |
Stack detection → brand context → keyword research → tech audit → roadmap + link inventory |
| Resume | docs/seo-machine.md exists |
Reads the tracker, picks the next pending phase (or one the user names), executes end-to-end through the quality gates |
Detection rule on every invocation: check docs/seo-machine.md at repo root (or the path recorded in .seo/config.json). No file → Initialize. File exists → Resume. The user does not need to remember which mode they're in.
Publishing Order (the load-bearing decision rule)
The roadmap orders patterns by conversion intent first, traffic intent second. This is the single most important decision the skill makes — it's why the alternatives + comparison pages ship before the playbooks + blog posts.
| Order | Pattern | Why | Cost |
|---|---|---|---|
| 1 | /alternatives/[competitor] (Pattern A) |
Highest conversion intent — the reader is already in market | ~4 hours per page |
| 2 | /compare/[a]-vs-[b] (Pattern D) |
Be the third option in any two-vendor comparison | ~3 hours per page |
| 3 | /for/[use-case] and /for/[audience] (Pattern B/C) |
JTBD without competitor name in query — high TP/volume ratio | ~4-5 hours per page |
| 4 | /playbooks/[topic] (Pattern E) |
Authority + AI-citation surface area + inbound link draw | ~2-3 days per page |
| 5 | /blog/... (out of scope here) |
Lowest conversion intent; defer until ~10 indexed pages exist | — |
What ships with it
23 files 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.
- assets/brand-template.md 2.1 KB
- assets/link-inventory-template.md 2.0 KB
- assets/roadmap-template.md 6.1 KB
- references/api-stack-recipes.md 10 KB
- references/exa-recipes.md 11 KB
- references/manual-research.md 4.0 KB
- references/methodology.md 5.8 KB
- references/off-page.md 5.4 KB
- references/patterns/alternatives.md 8.6 KB
- references/patterns/compare.md 5.9 KB
- references/patterns/playbooks.md 6.5 KB
- references/patterns/use-case.md 5.8 KB
- references/quality-bars.md 4.2 KB
- references/stacks/astro.md 5.1 KB
- references/stacks/detection.md 2.7 KB
- references/stacks/markdown-fallback.md 5.4 KB
- references/stacks/nextjs.md 4.9 KB
- references/stacks/rails-inertia.md 5.3 KB
- references/striking-distance.md 4.5 KB
- references/technical-audit.md 6.4 KB
- scripts/link_audit.py 9.9 KB runs code
- scripts/tech_audit.py 8.5 KB runs code
- scripts/word_count.py 4.5 KB runs code
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.
- 4d ago First seen · 334 lines · 216 tokens per session scan C 7982931378f5
seo-machine is a skill published in the GitHub repository MoizIbnYousaf/marketing-cli (31 stars, last pushed 21d ago), licensed MIT. It adds 216 tokens to every session and 5,086 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
citedy-content-writer
From topic to published blog post in one conversation — generate SEO- and GEO-optimized articles with AI illustrations and voice-over in 55 languages, create social media adaptations for 9 platforms, set up automated content sessions, and manage product knowledge base. End-to-end blog autopilot. Powered by Citedy.
citedy-trend-scout
Find what your audience is searching for right now — scout X/Twitter and Reddit for trending topics, discover and deep-analyze competitors, and find content gaps. Combine social signals with SEO intelligence. Powered by Citedy.
narrative-drift-monitor
Use when the user asks to "check if our surfaces have drifted from the canon", "watch for competitor repositioning", or "define when we should reposition"; produces a drift report — self-drift per flagship surface vs the narrative-registry canon over time (via wayback.py, change history Measured with as-of dates)…
launch-monitor
Use when the user asks to "monitor my launch", "track our Product Hunt / Hacker News ranking", or "watch the launch window"; runs the T-0 to T+30 window watch — pre-launch instrumentation verification (UTM/event checks, the upstream of RAMP P1), HN rank/points/comments polling with a comments-over-points flamewar…
launch-tier-planner
Use when the user asks to "plan my launch tier", "how big should this launch be", or "build a launch risk register with kill criteria"; produces a tier decision (Tier 1 flagship all-channel / Tier 2 targeted / Tier 3 changelog-level), a launch-type declaration (new-product / feature / relaunch / partnership with…
advocacy-program-designer
Use when the user asks to "design an employee advocacy program", "set up founder-led sharing", or "build a share kit for the team"; produces an advocacy program blueprint in two modes — participation-driven opt-in (default) or top-down assigned with its coercion and authenticity risks flagged — with a voluntary opt-in…