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 sanky369/vibe-building-skills --skill seo-strategygit clone --depth 1 https://github.com/sanky369/vibe-building-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/sanky369/vibe-building-skills/seo-strategy)<a href="https://agentmods.dev/skills/sanky369/vibe-building-skills/seo-strategy"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/seo-strategy/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/sanky369/vibe-building-skills/seo-strategy"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/seo-strategy.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.00133 | $0.02341 |
| Opus 5 | $0.00067 | $0.01171 |
| Sonnet 5 | $0.00027 | $0.00468 |
| Haiku 4.5 | $0.00013 | $0.00234 |
Grade A, and why
seo-strategy 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 13d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Strategy
Produce a written SEO strategy the user can execute immediately: where they can win (topical authority map + winnable keywords), what to publish (content pipeline), how to earn authority (links), and what technical floor must hold. Prime directive: only recommend fights the site can win. A "low difficulty" score is not the same as a winnable keyword — every recommendation must survive a manual SERP check.
When to use / when not to
- Use for site-level strategy: keyword targeting, content roadmaps, link building, SEO audits, "grow my organic traffic."
- If the user needs one article written, hand off to
skills/marketing/seo-content(bring the target keyword and intent with you). - If the user only needs a keyword list, not a full strategy, use
skills/marketing/keyword-research. - If the user's real problem is messaging or conversion, not traffic, route to
skills/marketing/positioning-anglesorskills/marketing/direct-response-copy.
Intake
Ask in one batch, only what's missing:
- Site URL and what the business sells (and to whom).
- Current state — roughly how much organic traffic, any existing content, domain age. Access to Google Search Console data if available.
- Topics of genuine expertise — what could they credibly write 20+ articles about?
- Constraints — content capacity (articles per month they can realistically produce/review) and budget for tools or outreach.
Infer from the site itself whenever you can (crawl/fetch it, inspect existing pages). If the user gives a URL and a one-line goal, state your assumptions about the rest and proceed — don't stall.
Workflow
1. Situate the site
Classify the site, because it changes everything downstream:
- New/weak site (little content, few links) → strategy is long-tail winnable keywords only (KGR-qualified), heavy topical clustering, foundational links.
- Established site with content that doesn't rank → strategy leads with a content audit: fix intent mismatches, consolidate cannibalizing pages, internal linking, then expand.
- Ranking site that plateaued → strategy leads with link building and topical gap-filling against the top competitor.
What ships with it
1 file 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.
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.
- 13d ago First seen · 151 lines · 133 tokens per session scan A 1c98b4c2c52f
seo-strategy is a skill published in the GitHub repository sanky369/vibe-building-skills (30 stars, last pushed 2mo ago), licensed MIT. It adds 133 tokens to every session and 2,341 once invoked, about $0.0007 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
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
dep-auditor
A read-only audit of a project’s third-party packages for known security issues, version health, and license facts. It uses the versions actually selected by lockfiles, which record the exact packages installed, rather than relying only on version ranges.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
zh-readme
A tool for writing README files in Chinese after first examining a software project. A README is the main guide visitors see when they open a code repository.
env-manager
An environment-variable manager for project settings stored outside the code, often in .env files. It checks variable definitions and usage while keeping secret values out of reports and terminal output.