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 Humblytics/humblytics-marketing-skills --skill seo-strategistgit clone --depth 1 https://github.com/Humblytics/humblytics-marketing-skillsWrote 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/humblytics/humblytics-marketing-skills/seo-strategist)<a href="https://agentmods.dev/skills/humblytics/humblytics-marketing-skills/seo-strategist"><img src="https://agentmods.dev/badge/skills/humblytics/humblytics-marketing-skills/seo-strategist/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/humblytics/humblytics-marketing-skills/seo-strategist"><img src="https://agentmods.dev/badge/skills/humblytics/humblytics-marketing-skills/seo-strategist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00082 | $0.01758 |
| Opus 5 | $0.00041 | $0.00879 |
| Sonnet 5 | $0.00016 | $0.00352 |
| Haiku 4.5 | $0.00008 | $0.00176 |
Grade A, and why
seo-strategist 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 12d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Strategist
Purpose
Build an SEO strategy grounded in keyword data, competitor analysis, on-page optimization, and technical health. Produces prioritized roadmaps ranked by traffic potential × winnability — not vanity keyword lists. Bridges technical SEO, content strategy, and conversion intent.
When to Use
- Building a content calendar backed by keyword research
- Auditing an existing site's SEO health before a relaunch
- Researching keywords for a new product or landing page
- Identifying content gaps vs competitors
- Diagnosing a traffic drop or ranking loss
- Planning a link-building or topical authority strategy
Before You Start
- Goal clarity — Traffic? Leads? Rankings for specific queries? Brand vs non-brand?
- Target audience — B2B? B2C? Geographic focus? Language?
- Current baseline — Google Search Console data (impressions, clicks, top queries)
- Competitive set — 3-5 direct and indirect competitors to benchmark against
- Tool access — Ahrefs / Semrush / GSC access; if none, note assumptions
- Site crawlability — Technical SEO audit requires a crawl (Screaming Frog, Sitebulb, or Ahrefs Site Audit)
Core Workflow
Step 1: Keyword Research with Intent Clustering
Don't chase keywords in isolation. Cluster by search intent:
| Intent | Query Pattern | Content Type | Conversion Distance |
|---|---|---|---|
| Informational | "how to", "what is", "guide" | Blog post, guide | Far (top-of-funnel) |
| Navigational | "[brand] login", "[product] pricing" | Brand pages | Close (if on-brand) |
| Commercial | "best X", "X vs Y", "X review" | Comparison, listicle | Mid-funnel |
| Transactional | "buy X", "X free trial", "[tool] tool" | Product page, pricing | Close |
For each cluster, rank by:
- Search volume (monthly searches)
- Keyword difficulty (how hard to rank — KD score)
- Traffic potential (not just volume — includes SERP features, CTR)
- Business relevance (does the query match your buyer?)
- Current position (if already ranking, how close to top 3?)
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.
- 12d ago First seen · 174 lines · 82 tokens per session scan A c7a59d5ae38d
seo-strategist is a skill published in the GitHub repository Humblytics/humblytics-marketing-skills (84 stars, last pushed 8d ago), licensed MIT. It adds 82 tokens to every session and 1,758 once invoked, about $0.0004 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
ab-test-generator
Generate A/B test variants for affiliate content. Triggers on: "create A/B test", "test my headline", "optimize my CTA", "generate variants", "split test ideas", "improve click-through rate", "test my landing page copy", "headline alternatives", "CTA variations", "which version is better", "optimize conversions"…
authoring-ci-workflows
Use when adding or editing a GitHub Actions workflow, composite action, or reusable workflow under .github/ — new CI jobs, triggers, matrices, checkout/clone tuning, action pinning, GitHub App token auth, concurrency groups, timeout-minutes, paths filters, caching, or runner choice. Covers PostHog's workflow-authoring…
isolating-product-facade-contracts
Plan and execute product isolation migrations to a facade plus contract layer in PostHog, following the Visual review architecture. Use when a product still exposes internals (models/logic/views) across boundaries and needs migration toward contracts.py + facade/api.py + presentation separation, with a PR strategy…
triaging-merge-queue-failures
Decision procedure for a PR that failed or was removed from the Trunk merge queue: classify the kick (superseded by a newer commit, not mergeable, a gate that failed on a cancelled run, real failure, one-off flake, or repo-wide flaky/infra issue) and take the matching action (wait, hold and fix, requeue once, or…
debugging-mcp-analytics
Debug, support, and build PostHog MCP Analytics — product analytics for MCP servers (the @posthog/mcp and posthog.mcp SDKs plus the mcpanalytics product). Use when MCP analytics data looks wrong or missing ("events aren't showing", "intent clusters are empty", "sessions are missing", "per-tool numbers look wrong")…
debugging-ci-failures
Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?"). Use when the user asks why CI is red, asks for the current CI or master status, or mentions a failing check, GitHub Actions run…