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 openseo-project-setupgit 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/openseo-project-setup)<a href="https://agentmods.dev/skills/moizibnyousaf/marketing-cli/openseo-project-setup"><img src="https://agentmods.dev/badge/skills/moizibnyousaf/marketing-cli/openseo-project-setup.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.00106 | $0.01512 |
| Opus 5 | $0.00053 | $0.00756 |
| Sonnet 5 | $0.00021 | $0.00302 |
| Haiku 4.5 | $0.00011 | $0.00151 |
Grade B, and why
openseo-project-setup scanned grade B 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 8d 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
- `configured: false` → name the missing envs from `missing_envs`. Hosted path: sign up at openseo.so, connect the MCP in the user's agent client (root `.mcp.json` ships the `openseo` server), and/or set `OPENSEO_API_KEY How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSEO Project Setup
Bind the current repo to an OpenSEO project so every other openseo-* skill has a stable project id, and prepare mktg's local SEO state contract. This is a one-time-per-repo handshake, not an audit and not research.
On Activation
Run these steps in order. Each has a fallback; never block on missing context.
Step 1 — Check catalog readiness
mktg catalog info openseo --json --fields configured,missing_envs,mcp
- Exit 1 → the openseo catalog is missing; upgrade marketing-cli. Stop.
configured: false→ name the missing envs frommissing_envs. Hosted path: sign up at openseo.so, connect the MCP in the user's agent client (root.mcp.jsonships theopenseoserver), and/or setOPENSEO_API_KEYfor non-interactive automation. Without any connection, stop after writing the gap note — research skills will fall back to Exa with metricsunknown.
Step 2 — Read brand grounding
Read brand/keyword-plan.md and brand/positioning.md if they exist (tolerate missing). The domain, audience, and positioning facts go into the project record. If brand/ is all templates, note it and recommend /cmo foundation first — SEO inputs without positioning are guesses.
Step 3 — Resolve the OpenSEO project
Via the OpenSEO MCP tools: whoami (if available) then list_projects. Match the project to the user's domain. If the list is ambiguous, ask which project. If MCP is unavailable but OPENSEO_API_KEY is set, note that interactive MCP steps are deferred and record what is known.
Do NOT call research tools to test connectivity — whoami/list_projects are the only probes allowed here (they are free; research calls spend DataForSEO credit).
Step 4 — Write the binding + state directories
Create or update .seo/openseo.json:
{ "version": 1, "projectId": "<id>", "domain": "<domain>", "mcpUrl": "https://app.openseo.so/mcp", "linkedAt": "<iso>", "updatedAt": "<iso>" }
Create .seo/ with rank-snapshots/ if rank tracking is in scope. If brand/keyword-plan.md is a template, leave it alone — the first research run populates it; do not pre-fill with placeholders.
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.
- 8d ago First seen · 115 lines · 106 tokens per session scan B 522476b134b6
openseo-project-setup is a skill published in the GitHub repository MoizIbnYousaf/marketing-cli (31 stars, last pushed 21d ago), licensed MIT. It adds 106 tokens to every session and 1,512 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (reads mcp configuration). 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 …