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-pack-local-servicesgit 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-pack-local-services)<a href="https://agentmods.dev/skills/psyduckler/aeo-skills/aeo-pack-local-services"><img src="https://agentmods.dev/badge/skills/psyduckler/aeo-skills/aeo-pack-local-services/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-pack-local-services"><img src="https://agentmods.dev/badge/skills/psyduckler/aeo-skills/aeo-pack-local-services.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.00113 | $0.00765 |
| Opus 5 | $0.00056 | $0.00382 |
| Sonnet 5 | $0.00023 | $0.00153 |
| Haiku 4.5 | $0.00011 | $0.00076 |
Grade A, and why
aeo-pack-local-services 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AEO Pack: Local Services
Source: github.com/psyduckler/aeo-skills Part of: AEO Skills Suite (v2 prompt packs) Schema: prompt-pack-v1
16 ready-to-track prompts for local service business visibility, covering the journey from "find a provider near me" to "is this one trustworthy?"
Template variables
| Variable | Required | Example |
|---|---|---|
service |
yes | plumber, dentist, lawyer, mechanic, restaurant, electrician |
city |
yes | Austin, San Francisco, Brooklyn |
specialty |
no | emergency, family, criminal, pediatric |
neighborhood |
no | South Congress, Mission District |
How to use this pack
npx skills add psyduckler/aeo-skills --skill aeo-pack-local-services
Then merge the filled-in prompts from prompts.json into your aeo.config.json. Example for an Austin-area emergency plumbing service:
| Template | Filled |
|---|---|
Best {{service}} in {{city}} |
Best plumber in Austin |
Emergency {{service}} {{city}} |
Emergency plumber Austin |
{{service}} reviews {{city}} |
plumber reviews Austin |
How much does a {{service}} cost in {{city}}? |
How much does a plumber cost in Austin? |
Why these prompts
Local-service AI search splits differently than B2B:
- Proximity + service is the dominant pattern. "best plumber in Austin" is the canonical query.
- Trust signals (reviews, licensure, "trustworthy") matter more than in B2B — high cost of choosing wrong.
- Urgency matters (emergency / open now) — Gemini's grounding behavior shifts for time-sensitive intent.
- Educational queries ("what to expect from a {{service}} visit") drive top-of-funnel awareness even when the user isn't actively shopping.
Notes
- This pack pairs with local SEO best practices: Google Business Profile, NAP (Name/Address/Phone) consistency, review acquisition. AEO visibility tracks the AI-Overview side; classical local SEO drives the citations Gemini surfaces.
- Add
LocalBusinessJSON-LD via aeo-schema to improve machine-readability of the business page. - Suggested first-baseline scope: 8–10 prompts × 20 samples = ~$0.05 estimated cost.
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 · 60 lines · 113 tokens per session scan A 0cb849ecffe0
aeo-pack-local-services is a skill published in the GitHub repository psyduckler/aeo-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 113 tokens to every session and 765 once invoked, about $0.0006 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…