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 itallstartedwithaidea/agent-skills --skill keyword-researchgit clone --depth 1 https://github.com/itallstartedwithaidea/agent-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/itallstartedwithaidea/agent-skills/keyword-research)<a href="https://agentmods.dev/skills/itallstartedwithaidea/agent-skills/keyword-research"><img src="https://agentmods.dev/badge/skills/itallstartedwithaidea/agent-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/itallstartedwithaidea/agent-skills/keyword-research"><img src="https://agentmods.dev/badge/skills/itallstartedwithaidea/agent-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.00025 | $0.02087 |
| Opus 5 | $0.00013 | $0.01043 |
| Sonnet 5 | $0.00005 | $0.00417 |
| Haiku 4.5 | $0.00003 | $0.00209 |
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 10d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Keyword Research
Part of Agent Skills™ by googleadsagent.ai™
Description
The Keyword Research skill delivers a systematic approach to keyword discovery, expansion, and optimization for Google Ads campaigns. Starting from seed keywords, it builds comprehensive keyword universes through multiple expansion vectors: semantic variations, competitor keyword mining, search term report analysis, long-tail discovery, and intent-based grouping. The result is a structured keyword strategy that maximizes relevant coverage while minimizing wasted spend.
Match type selection is a critical component. The skill evaluates each keyword against conversion probability, search volume, competition intensity, and cost-per-click economics to recommend the optimal match type. Broad match keywords are paired with smart bidding strategies, phrase match captures high-intent variations, and exact match locks in proven converters. The skill continuously refines match type assignments based on search term report feedback loops.
Negative keyword management is equally important. The skill mines search term reports for irrelevant queries, builds hierarchical negative keyword lists (account-level, campaign-level, ad-group-level), and maintains shared negative keyword lists across campaigns. Proactive negative keyword discovery prevents budget waste before it occurs by identifying common irrelevant query patterns for each industry vertical.
Use When
- User asks for "keyword research" or "keyword ideas"
- User wants to "expand keywords" or "find new keywords"
- User mentions "negative keywords" or "search term mining"
- User asks about "match types" (broad, phrase, exact)
- User wants to "reduce wasted spend" on irrelevant queries
- User asks to "build a keyword list" or "keyword strategy"
- User mentions "keyword grouping" or "ad group structure"
- User wants "long-tail keywords" or "low competition keywords"
- User asks to "analyze search terms" or "query mining"
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.
- 10d ago First seen · 227 lines · 25 tokens per session scan A 20d7ab29288c
keyword-research is a skill published in the GitHub repository itallstartedwithaidea/agent-skills (37 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 2,087 once invoked, about $0.0001 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
x-tweet-by-conversation
Collects every tweet in an X (Twitter) conversation thread given a conversation id (root tweet id) — the focal tweet plus all replies, sub-replies, and quote chains — and returns normalized per-tweet data with text, author, engagement counts, media, hashtags, mentions, inreplyto mapping, and cursor for pagination. Use…
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.