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 keyword-researchgit 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/keyword-research)<a href="https://agentmods.dev/skills/sanky369/vibe-building-skills/keyword-research"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/keyword-research/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/keyword-research"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/keyword-research.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.00121 | $0.01692 |
| Opus 5 | $0.00060 | $0.00846 |
| Sonnet 5 | $0.00024 | $0.00338 |
| Haiku 4.5 | $0.00012 | $0.00169 |
Grade A, and why
keyword-research 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Keyword Research
Produce a keyword map: a scored, clustered list of search terms worth targeting, each tied to the content that should win it. Governing principle: a keyword is only worth targeting if it survives all six circles — aligned with the positioning, phrased in the customer's language, under-served by competitors, actually searched, winnable with the user's real expertise, and connected to revenue. Traffic that fails circle 6 is vanity.
When to use / when not to
- Use before writing SEO content, when planning a content calendar, or when the user wants to know what their audience searches for.
- If no positioning statement exists, run
skills/marketing/positioning-anglesfirst (or infer a provisional one and label it) — circle 1 is unworkable without it. - If the user wants the full organic program — link building, technical SEO, programmatic pages, domain authority — use
skills/marketing/seo-strategy; this skill is the keyword-selection layer only. - If keywords already exist and the user wants the article written, go straight to
skills/marketing/seo-content.
Intake
One batch; reuse anything already produced by skills/marketing/orchestrator or skills/marketing/positioning-angles:
- Your positioning statement (or: what you sell, to whom, and what makes it different).
- Your 2–3 closest competitors' websites.
- Any sources of raw customer language — support tickets, sales calls, reviews, community threads — or paste examples of how customers describe the problem.
- Site status: domain age, roughly how much content published, any current rankings? (Determines how competitive a keyword you can win.)
- Access to a keyword tool (Ahrefs, Semrush, Google Keyword Planner)? If yes, the user runs volume lookups when asked; if no, proceed with estimates.
Don't stall: with a positioning statement and a recognizable market you can draft the full map from knowledge and web research — label all volumes and difficulty as estimates and list them for the user to verify in a tool.
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 · 103 lines · 121 tokens per session scan A 275c62d6e231
keyword-research is a skill published in the GitHub repository sanky369/vibe-building-skills (30 stars, last pushed 2mo ago), licensed MIT. It adds 121 tokens to every session and 1,692 once invoked, about $0.0006 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.