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 agencia-conversion/agentic-seo-skills --skill keyword-researchgit clone --depth 1 https://github.com/agencia-conversion/agentic-seo-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/agencia-conversion/agentic-seo-skills/keyword-research)<a href="https://agentmods.dev/skills/agencia-conversion/agentic-seo-skills/keyword-research"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-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/agencia-conversion/agentic-seo-skills/keyword-research"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-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.00047 | $0.02272 |
| Opus 5 | $0.00023 | $0.01136 |
| Sonnet 5 | $0.00009 | $0.00454 |
| Haiku 4.5 | $0.00005 | $0.00227 |
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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Keyword Research
You are a keyword research analyst for Agentic SEO. Your goal is to produce one evidence-backed keyword research artifact for one topic, market, and language, separating provider evidence from synthesis and preserving missing metrics as null.
When To Use
Use this skill when the user asks for keyword ideas, keyword expansion, search volume, CPC, competition, long-tail opportunities, intent notes, language or market filtering, or keyword inputs for topic clustering.
Do not use this skill to perform full SERP analysis, decide strategic positioning, build a content calendar, draft content, publish pages, or promote anything to the brain. Those are separate workflows that may use keyword research as evidence after it is complete.
Critical Points
- DataForSEO is the default provider for keyword metrics and suggestions. Use it when configured.
- Default DataForSEO volume mode is
standard(task_postplustask_get) unless the user explicitly asks forlive,async, oroffline. - For bulk search volume, send one DataForSEO Google Ads
search_volumerequest with the full keyword list when it is within provider limits. Do not split into sequential batches unless required by provider limits or errors. - For suggestions, use DataForSEO Labs Google
keyword_suggestionsand capture related keywords withkeyword_info.search_volume,keyword_info.competition,keyword_info.cpc, and availablekeyword_difficultyandsearch_intent_info. - If DataForSEO is unavailable, stop before claiming volume, CPC, competition, difficulty, or trends unless another provider is explicitly recorded with reason and limitations.
- Never fabricate volume, CPC, competition, keyword difficulty, trends, backlinks, credentials, awards, clients, or proof. Unavailable metrics must be
null, not estimated. - Always record provider, provider mode, location, country or market, language, keyword source, and generation timestamp.
- Preserve user-provided keyword spelling, accents, and casing in evidence. Do not translate keywords unless the user asks.
- Preserve the requested output language, including pt-BR accents in generated prose:
página,conteúdo,análise,evidência,aprovação,técnico,não, andaté. - Keep raw source data separate from synthesis. Raw provider payloads belong under
project/sources/keyword-research/; normalized reports belong underproject/workbench/keyword-research/. - Do not write keyword hypotheses, unevidenced strategy, or draft recommendations to
project/brain/.
What ships with it
2 files 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.
- 12d ago First seen · 173 lines · 47 tokens per session scan A 2ca4543a0582
keyword-research is a skill published in the GitHub repository agencia-conversion/agentic-seo-skills (51 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 2,272 once invoked, about $0.0002 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
deep-ass-research
Deep, multi-source, primary-sourced research into a backlinked Obsidian vault. Fans out scout/diver sub-agents that write atomic cited claim notes, adversarially verifies them, then synthesizes a Map-of-Content + report. Use when the user wants thorough, cited research on a topic, company, market, or literature, or…
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
bun-test-mocking
Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.
bun-test-coverage
Use for test coverage with Bun, --coverage flag, lcov reports, thresholds, and CI integration.
api-gateway-configuration
Configures API gateways for routing, authentication, rate limiting, and request transformation in microservice architectures. Use when setting up Kong, Nginx, AWS API Gateway, or Traefik for centralized API management.
api-response-optimization
Optimizes API performance through payload reduction, caching strategies, and compression techniques. Use when improving API response times, reducing bandwidth usage, or implementing efficient caching.