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 psyduckler/aeo-skills --skill aeo-prompt-question-findergit clone --depth 1 https://github.com/psyduckler/aeo-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/psyduckler/aeo-skills/aeo-prompt-question-finder)<a href="https://agentmods.dev/skills/psyduckler/aeo-skills/aeo-prompt-question-finder"><img src="https://agentmods.dev/badge/skills/psyduckler/aeo-skills/aeo-prompt-question-finder/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/psyduckler/aeo-skills/aeo-prompt-question-finder"><img src="https://agentmods.dev/badge/skills/psyduckler/aeo-skills/aeo-prompt-question-finder.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.00086 | $0.00471 |
| Opus 5 | $0.00043 | $0.00235 |
| Sonnet 5 | $0.00017 | $0.00094 |
| Haiku 4.5 | $0.00009 | $0.00047 |
Grade A, and why
aeo-prompt-question-finder 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.
What it actually says
Prompt Question Finder
Discover what questions people ask about a topic by querying Google Autocomplete with question modifiers.
Usage
Run the script from the skill directory:
python3 scripts/find_questions.py "travel itinerary"
Options
--modifiers what how why should— override default modifiers (default: what how why should can does is when where which will are do)--delay 0.5— seconds between requests (use 0.5–1.0 when running many topics in batch)--json— output as JSON for programmatic use--volume— fetch avg monthly search volume via DataForSEO (reads creds from macOS Keychain:dataforseo-login/dataforseo-password, or env varsDATAFORSEO_LOGIN/DATAFORSEO_PASSWORD)--location 2840— DataForSEO location code (default: 2840 = US)--lang en— language code for volume lookup (default: en)
Examples
# Default modifiers (what, how, why)
python3 scripts/find_questions.py "protein powder"
# Custom modifiers
python3 scripts/find_questions.py "travel itinerary" --modifiers what how why should when
# JSON output
python3 scripts/find_questions.py "travel itinerary" --json
Rate Limits
Google Autocomplete is an unofficial endpoint. Single-topic runs (10 requests) are safe. When running multiple topics in batch or parallel, always use --delay 0.5 or higher to avoid temporary IP blocks.
How It Works
For each modifier, the script queries https://suggestqueries.google.com/complete/search with "{modifier} {topic}" and returns the autocomplete suggestions. No API key required.
What ships with it
1 file 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 · 47 lines · 86 tokens per session scan A 904e57bcfedf
aeo-prompt-question-finder is a skill published in the GitHub repository psyduckler/aeo-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 471 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…