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 JustineDevs/premortem --skill find-keywordsgit clone --depth 1 https://github.com/JustineDevs/premortemWrote 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/justinedevs/premortem/find-keywords)<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.
<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>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.00072 | $0.01913 |
| Opus 5 | $0.00036 | $0.00957 |
| Sonnet 5 | $0.00014 | $0.00383 |
| Haiku 4.5 | $0.00007 | $0.00191 |
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 9d 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.
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.
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):
- Domain and goal. What site is this for? What is the primary conversion (leads, sign-ups, sales, traffic)?
- Seed topic. The core subject area — not a single keyword but the business category (e.g., "project management software", "personal injury law Chicago").
- Existing rankings. Does the site already rank for terms in this area? Existing rankings tell you where to defend vs. expand.
- 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:
- Search
site:yourdomain.com [keyword]— does an existing page already target this term? - Check Google Search Console — is an existing page already getting impressions for this keyword?
- If yes: update the existing page instead of creating a new one.
- 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)
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.
- 9d ago First seen · 207 lines · 72 tokens per session scan A b6416e188c01
find-keywords is a skill published in the GitHub repository JustineDevs/premortem (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,913 once invoked, about $0.0004 per session on Opus 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.
Other skills, from other repositories
awesome-azd-template-submit
Submit an azd template to the awesome-azd gallery. Use when asked to submit, add, or contribute a template to awesome-azd. Requires only a GitHub repository URL — all metadata (title, description, languages, frameworks, Azure services, IaC) is auto-detected by the submission pipeline.
azure-cli
Use the Azure CLI to manage subscriptions, resource groups, AKS, App Service, Key Vault, and role assignments.
bitbottle
Reference for the bitbottle CLI — a gh-style tool for Bitbucket Server/DC and Cloud. Load when the user asks about bitbottle commands, auth setup, PRs, repos, branches, tags, commits, pipelines, or why a command failed. Load even if the user just says "bitbottle", mentions "Bitbucket", or pastes a bitbottle error…
azure-cli
A command-line tool for managing Microsoft Azure, Microsoft's cloud platform, from a terminal. It covers account sign-in, subscriptions, resource groups, virtual machines, and other cloud resources.
extract-api
This skill should be used when the user asks to "extract API from", "import API from", "add commands from this repo", "register API from docs", "convert docs to CLI commands", "import Postman collection", or provides a GitHub repository URL, a documentation site URL, a Postman collection file/URL, or a local API…
sidekick
ALWAYS run sdkck search FIRST before using ANY tool, MCP server, Bash command, or external API. sdkck is the canonical command surface for Jira, Sentry, MySQL, Postgres, Supabase, Bitbucket, Confluence, and imported OpenAPI/Postman specs. Trigger on every task involving external systems, APIs, databases, tickets…