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 agentmods add skills/hoangsonww/petswipe-match-app/map-geocoding-debugnpx skills add hoangsonww/PetSwipe-Match-App --skill map-geocoding-debuggit clone --depth 1 https://github.com/hoangsonww/PetSwipe-Match-AppWrote 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/hoangsonww/petswipe-match-app/map-geocoding-debug)<a href="https://agentmods.dev/skills/hoangsonww/petswipe-match-app/map-geocoding-debug"><img src="https://agentmods.dev/badge/skills/hoangsonww/petswipe-match-app/map-geocoding-debug.svg" alt="Measured on agentmods" 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 | $0.00064 | $0.00248 |
| Opus 5 | $0.00032 | $0.00124 |
| Sonnet 5 | $0.00013 | $0.00050 |
| Haiku 4.5 | $0.00006 | $0.00025 |
Grade A, and why
map-geocoding-debug 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 5d 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
Use this skill for map and geocoding issues.
Workflow
- Start from
frontend/pages/map.tsx. - Trace how location strings are generated, normalized, cached, and rendered.
- Check whether the frontend is calling the local proxy or an external geocoder directly.
- Check request amplification, duplicate queries, fallback queries, and cache-miss behavior.
- Validate any fixes without introducing responsive or chart-like overflow regressions on the page.
Repo-Specific Guidance
- The map page and the frontend geocode API route are the primary touchpoints.
- Request explosion and low-signal fallback queries are a known class of issue in this repo.
- CORS or upstream slowness should be treated separately from local query-generation bugs.
If the issue is large, spawn map_debugger first.
Read references/map-debug-checklist.md.
What ships with it
2 files 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.
- 5d ago First seen · 25 lines · 64 tokens per session scan A 420950e5f38c
map-geocoding-debug is a skill published in the GitHub repository hoangsonww/PetSwipe-Match-App (24 stars, last pushed 19d ago), licensed MIT. It adds 64 tokens to every session and 248 once invoked, about $0.0003 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
aws-best-practices
No-web local AWS best-practices catalog. Use the local catalog files first and do not browse, search the web, open AWS docs, or use live documentation tools for ordinary answers unless the user explicitly asks for live/current verification or the local file is missing. Trigger when the user needs AWS best practices…
prowler-ui
Prowler UI-specific patterns. For generic patterns, see: typescript, react-19, nextjs-16, tailwind-4. Trigger: When working inside ui/ on Prowler-specific conventions (shadcn, folder placement, actions/adapters, shared types/hooks/lib).
prowler-test-api
Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
prowler-mcp
Creates MCP tools for Prowler MCP Server. Covers BaseTool pattern, model design, and API client usage. Trigger: When working in mcpserver/ on tools (BaseTool), models (MinimalSerializerMixin/fromapiresponse), or API client patterns.
document-service
This skill should be used when the user asks to "analyze this codebase", "document this service", "generate technical docs", "I inherited this code", "help me understand this system", "create docs for this project", "what does this system look like", "onboard me to this codebase", "this codebase has no docs"…