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 off-page-seogit 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/off-page-seo)<a href="https://agentmods.dev/skills/moizibnyousaf/marketing-cli/off-page-seo"><img src="https://agentmods.dev/badge/skills/moizibnyousaf/marketing-cli/off-page-seo/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/off-page-seo"><img src="https://agentmods.dev/badge/skills/moizibnyousaf/marketing-cli/off-page-seo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 222 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 223 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 224 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00204 | $0.03217 |
| Opus 5 | $0.00102 | $0.01608 |
| Sonnet 5 | $0.00041 | $0.00643 |
| Haiku 4.5 | $0.00020 | $0.00322 |
Grade A, and why
off-page-seo 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Off-Page SEO
On-page work caps out around DR + 20 in achievable KD targets. Off-page work expands that ceiling. This skill generates a prioritized backlink target list across three lanes — directories, listicles, guest posts — and a starter-stack checklist of universal SaaS submission flows. It does not submit anything. The user (or the user's outreach team) does the actual submission.
The off-page half of the SEO operation. Pairs with seo-machine (on-page programmatic sprint) — ship pages with seo-machine, queue outreach with this skill, run them in parallel.
On Activation
- Load brand context:
positioning.md,competitors.md,audience.md,voice-profile.md. Missing files are fine. - Surface what loaded:
Backend Selection
Prefer OpenSEO get_backlinks_overview / get_domain_overview and openseo-link-prospecting outputs when configured; otherwise Exa/web with authority metrics unknown. Full contract: skills/openseo/references/backend-contract.md.
Brand context loaded:
├── Positioning ✓/✗ (drives outreach angle + value-add framing)
├── Competitors ✓/✗ (target list source — Recipe F runs on them)
├── Audience ✓/✗ (selects niche-specific directories + communities)
└── Voice Profile ✓/✗ (shapes outreach email tone if user chains into cold-email)
- If
competitors.mdis missing, prompt the user for 3-7 direct competitors before running Recipe F (the researched-target-list recipe needs competitor domains as input). - Check for
.seo/backlink-targets.jsonin the current project. If present, this is a re-run — show the user the existing target counts and ask whether to refresh or just present the existing list.
When to use vs adjacent skills
| Skill | When | When NOT |
|---|---|---|
off-page-seo (this) |
Building a prioritized backlink target list + universal starter-stack checklist | Doing actual outreach (use cold-email for that) |
seo-machine |
On-page programmatic sprint (alternatives, comparison, use-case pages) | Off-page work — this skill |
seo-audit |
Diagnosing on-site technical issues | Building backlink target lists |
cold-email (in direct-response-copy) |
Writing the outreach emails after target list exists | Generating the target list itself |
startup-launcher |
Launch-day platform submissions (Product Hunt, BetaList, etc.) | Ongoing backlink work post-launch |
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 · 225 lines · 204 tokens per session scan A 0fc2c1e40c0a
off-page-seo is a skill published in the GitHub repository MoizIbnYousaf/marketing-cli (31 stars, last pushed 22d ago), licensed MIT. It adds 204 tokens to every session and 3,217 once invoked, about $0.0010 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 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-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…
engagement-inbox-manager
Use when the user asks to "triage our comments, DMs, and mentions", "draft replies to this thread", "can we repost this fan post", or "set up inbox SLAs and an escalation path"; produces a ranked triage queue with register detection (sincere / ironic / performative / parasocial, sentiment-inversion table included …