PetSwipe-Match-App: Skill for Codex

.agents/skills/map-geocoding-debug/SKILL.md

map-geocoding-debug is a skill for Codex from hoangsonww/PetSwipe-Match-App. It costs 64 tokens per session (248 once invoked), scanned A, original, MIT.

A PetSwipe-specific guide for diagnosing map and geocoding problems. Geocoding converts a place name or address into map coordinates, while caching stores previous results to avoid repeated requests.

In plain words
What is it for?
Use it when map results are wrong, geocoding requests are duplicated or excessive, cached results behave unexpectedly, or the location UI regresses.
Why use it?
It helps separate frontend query bugs from proxy, CORS, upstream service, caching, and performance problems.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is hoangsonww/PetSwipe-Match-App's own configuration. It tells Codex how to work on PetSwipe-Match-App itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything PetSwipe-Match-App configures →

Reuse

Borrowing it

Nothing to install: this file belongs to hoangsonww/PetSwipe-Match-App. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/hoangsonww/PetSwipe-Match-App/master/.agents/skills/map-geocoding-debug/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/hoangsonww/PetSwipe-Match-App

Made for: 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 map-geocoding-debug

README.md
[![agentmods](https://agentmods.dev/badge/skills/hoangsonww/petswipe-match-app/map-geocoding-debug/github.svg)](https://agentmods.dev/skills/hoangsonww/petswipe-match-app/map-geocoding-debug)
Your own site
<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/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 map-geocoding-debug

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 248 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 original No closer match found 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.00064 $0.00248
Opus 5.5 $0.00026 $0.00099
Sonnet 5.5 $0.00013 $0.00050
Haiku 4.5 $0.00006 $0.00025

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

Security

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 1mo 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.

.agents/skills/map-geocoding-debug/SKILL.md · 25 lines

What it actually says

Use this skill for map and geocoding issues.

Workflow

  1. Start from frontend/pages/map.tsx.
  2. Trace how location strings are generated, normalized, cached, and rendered.
  3. Check whether the frontend is calling the local proxy or an external geocoder directly.
  4. Check request amplification, duplicate queries, fallback queries, and cache-miss behavior.
  5. 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.

Files

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.

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. 1mo ago First seen · 25 lines · 64 tokens per session scan A 420950e5f38c

Subscribe to this mod's changes

map-geocoding-debug is a skill published in the GitHub repository hoangsonww/PetSwipe-Match-App (26 stars, last pushed 28d ago), licensed MIT. It adds 64 tokens to every session and 248 once invoked, about $0.0003 per session on Opus 5.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.

Related

Other skills, from other repositories

agentcore-investigation

Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.

awslabs/mcp · 52 tokens

postgresql-indexing

PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing…

prowler-cloud/prowler · 108 tokens

gh-aw

Create and maintain GitHub Agentic Workflows (gh-aw) for Prowler. Trigger: When creating agentic workflows, modifying gh-aw frontmatter, configuring safe-outputs, setting up MCP servers in workflows, importing Copilot Custom Agents, or debugging gh-aw compilation.

prowler-cloud/prowler · 59 tokens

tdd

Test-Driven Development workflow for ALL Prowler components (UI, SDK, API). Trigger: ALWAYS when implementing features, fixing bugs, or refactoring - regardless of component. This is a MANDATORY workflow, not optional.

prowler-cloud/prowler · 50 tokens

hyperpod-node-debugger

Diagnose and remediate per-node issues on a HyperPod cluster (EKS or Slurm) — a specific node is unhealthy, unresponsive, stuck, or needs replacing. Covers on-node EFA, GPU / accelerator hardware (XID, ECC, NVLink, row-remap, DCGM), Slurm node down/drained, disk and memory pressure, per-node lifecycle-script failures…

awslabs/agent-plugins · 139 tokens

hyperpod-cluster-debugger

Diagnose and remediate cluster-wide HyperPod (EKS or Slurm) problems — creation / deployment failures (CloudFormation, EFA health check, lifecycle scripts, capacity), EKS access, node replacement, CloudFormation nested-stack errors, post-maintenance rollback state, dangling nodes, autoscaler conflicts. Includes…

awslabs/agent-plugins · 80 tokens