find-keywords

find-keywords is a skill for Claude Code, Codex from JustineDevs/premortem. It costs 72 tokens per session (1,913 once invoked), scanned A, a copy of find-keywords, Apache-2.0.

A keyword-research workflow for building and prioritising search terms around a website, topic, or campaign. It groups terms by the reason people search for them and considers existing rankings.

In plain words
What is it for?
Use it to create keyword lists, map search intent, check for competing pages on the same site, and seed topic groups.
Why use it?
It helps avoid targeting terms that duplicate existing pages and focuses content work on realistic search opportunities.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to create keyword lists, map search intent, check for competing pages on the same site, and seed topic groups.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/justinedevs/premortem/find-keywords
Install

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.

Any agent
npx skills add JustineDevs/premortem --skill find-keywords
Clone the repo
git clone --depth 1 https://github.com/JustineDevs/premortem

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for find-keywords

README.md
[![agentmods](https://agentmods.dev/badge/skills/justinedevs/premortem/find-keywords/github.svg)](https://agentmods.dev/skills/justinedevs/premortem/find-keywords)
Your own site
<a href="https://agentmods.dev/skills/justinedevs/premortem/find-keywords"><img src="https://agentmods.dev/badge/skills/justinedevs/premortem/find-keywords/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.

agentmods 80×15 button for find-keywords

Your own site · 80×15
<a href="https://agentmods.dev/skills/justinedevs/premortem/find-keywords"><img src="https://agentmods.dev/badge/skills/justinedevs/premortem/find-keywords.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,913 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00072 $0.01913
Opus 5.5 $0.00029 $0.00765
Sonnet 5.5 $0.00014 $0.00383
Haiku 4.5 $0.00007 $0.00191

Measured 2mo ago against content hash b6416e188c01, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

find-keywords 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 2mo 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.

Origin

This is a copy

100% identical to find-keywords — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/find-keywords/SKILL.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Find Keywords

Build a prioritized keyword universe from a seed topic using intent mapping, difficulty-adjusted opportunity scoring, and cluster seeding.

Before You Start

Gather this context (ask if not provided):

  1. Domain and goal. What site is this for? What is the primary conversion (leads, sign-ups, sales, traffic)?
  2. Seed topic. The core subject area — not a single keyword but the business category (e.g., "project management software", "personal injury law Chicago").
  3. Existing rankings. Does the site already rank for terms in this area? Existing rankings tell you where to defend vs. expand.
  4. Constraints. Budget, team size, content velocity — these determine whether to chase head terms or focus on long-tail.

Step 0: Cannibalization Screen

Before building a new keyword list, check what the site already targets. Creating a new page for a keyword you already rank for can split authority and hurt both pages.

For each keyword you're considering:

  1. Search site:yourdomain.com [keyword] — does an existing page already target this term?
  2. Check Google Search Console — is an existing page already getting impressions for this keyword?
  3. If yes: update the existing page instead of creating a new one.
  4. If multiple pages rank for the same keyword: you have a cannibalization problem. Consolidate before expanding.

Low-Hanging Fruit Check

Before chasing new keywords, look for existing wins:

  • Positions 11-20 — You're almost on page 1. These keywords need content improvements or better internal linking, not new pages.
  • High impressions, low clicks — Title/meta description optimization can unlock traffic without new content.
  • Declining positions — Keywords where you're losing ground may need content refreshes (see recover-content).

Address these before building net-new keyword lists.

Keyword Universe Construction

Build the universe in three tiers:

Tier 1 — Head Terms (high volume, high difficulty)

Read the full file on GitHub · 207 lines

Changes

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.

  1. 2mo ago First seen · 207 lines · 72 tokens per session scan A b6416e188c01

Subscribe to this mod's changes

find-keywords is a skill published in the GitHub repository JustineDevs/premortem (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,913 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to find-keywords, differing in 0 lines, and is treated as a copy.

Related

find-keywords compared with skills from other repositories

find-keywords next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
find-keywordsJustineDevs/premortemSkill23mo agoApache-2.0A72Claude Code, Codex
awesome-azd-template-submitAzure/awesome-azdSkill2733d agoMITA83Claude Code, Codex
bitbottleproggarapsody/bitbottleSkill317d agoMITA84Codex
extract-apihesedcasa/sdkckSkill9yesterdayApache-2.0C86Claude Code
sidekickhesedcasa/sdkckSkill9yesterdayApache-2.0C100Claude Code
azure-clichaterm/terminal-skillsSkill598mo agoApache-2.0A7Claude Code, Codex
aws-clielasticdotventures/_b00t_Skill1512d agononeA31Claude Code