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 syleedlabs/deal-locator-mcp --skill resolve-addressgit clone --depth 1 https://github.com/syleedlabs/deal-locator-mcpWrote 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/syleedlabs/deal-locator-mcp/resolve-address)<a href="https://agentmods.dev/skills/syleedlabs/deal-locator-mcp/resolve-address"><img src="https://agentmods.dev/badge/skills/syleedlabs/deal-locator-mcp/resolve-address/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/syleedlabs/deal-locator-mcp/resolve-address"><img src="https://agentmods.dev/badge/skills/syleedlabs/deal-locator-mcp/resolve-address.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00098 | $0.00751 |
| Opus 5 | $0.00049 | $0.00376 |
| Sonnet 5 | $0.00020 | $0.00150 |
| Haiku 4.5 | $0.00010 | $0.00075 |
Grade A, and why
resolve-address 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
주소 해석 (/resolve-address)
$ARGUMENTS 를 deal-locator MCP 의 resolve_address 에 그대로 넘겨 해석 결과를
정리해 답한다. 다른 도구가 주소를 못 잡을 때 원인을 찾는 진단 도구다.
1) 인자 해석
- 입력 전체가
query다. 손대지 말고 그대로 넘긴다 — 사용자가 준 원문이 왜 실패하는지 보는 게 목적이라, 임의로 고쳐 넘기면 진단이 안 된다. - 동만 줘도(
구로동 1128-1) 엔진이 구를 역추적한다.
2) 답변 규칙 (반드시 지킬 것)
-
lot_structure='조회실패'는 '단일 필지'가 아니라 '미확인'이다. 이 둘을 절대 섞지 마라. 조회실패를 단일 필지로 읽으면, 합필된 땅을 단일 필지로 오인해 면적·평단가 판단이 통째로 틀어진다. 미확인이면 **"확인하지 못했다"**고 그대로 말한다. -
부속지번이 있으면(합필) 그 사실을 먼저 말한다. 여러 필지가 한 건물을 이루면 대지면적이 대표지번 하나의 면적이 아니다 — 평단가 해석이 달라진다.
-
해석된 구가 사용자 기대와 다를 수 있다. 동 이름이 여러 구에 있으면 엔진이 하나를 고른다. 결과의 구를 반드시 노출해 사용자가 확인하게 한다.
-
이 도구는 실거래를 조회하지 않는다. 주소·필지 구조만 본다. 가격을 물으면
/deal-card로 넘긴다. -
status가OK가 아니면 사유를 그대로 전하고, 어떻게 고쳐 입력하면 되는지 구체적으로 안내한다(예:'구로구 구로동 1128-1'처럼 구를 함께).
3) 출력 형태
입력: "구로동 1128-1"
해석: 구로구 구로동 1128-1
법정동코드: 11530-10200
필지구성: 단일 필지 ← 또는 '대표+부속 3필지(합필)' / '확인 못함'
- 합필이면 부속지번을 나열한다.
- 해석 실패면 원인 + 고쳐 쓰는 법을 한 줄로 준다.
- 이어서 무엇을 할 수 있는지 안내한다 — 실거래는
/deal-card, 이력은/deal-history, 동네 시세는/area-scan.
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 · 54 lines · 98 tokens per session scan A 7a52d7d02687
resolve-address is a skill published in the GitHub repository syleedlabs/deal-locator-mcp (27 stars, last pushed 7d ago), licensed MIT. It adds 98 tokens to every session and 751 once invoked, about $0.0005 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…