What is landmark-navigation-assist?

A phone guide for the last part of a delivery or pickup journey to a known building. It uses a prepared location record and local landmarks, rather than relying only on a map pin or postal address.

Use it to guide delivery drivers or repeat ride-hailing pickups through the final few hundred metres to a configured building, with human escalation if they remain stuck.

GPS pins and written addresses can be unreliable in landmark-based, informally numbered, or newly built areas. The driver can describe their approach, receive matching turn-by-turn landmark directions, and confirm the building's identifying features.

landmark-navigation-assist — Skill by CALLE-AI

Install

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.

Any agent

npx skills add CALLE-AI/awesome-phone-call-agents --skill landmark-navigation-assist

Clone the repo

git clone --depth 1 https://github.com/CALLE-AI/awesome-phone-call-agents

Made for: Claude Code, 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/landmark-navigation-assist/github.svg)](https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/landmark-navigation-assist)

Your own site

<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/landmark-navigation-assist"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/landmark-navigation-assist/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/calle-ai/awesome-phone-call-agents/landmark-navigation-assist"><img src="https://agentmods.dev/badge/skills/calle-ai/awesome-phone-call-agents/landmark-navigation-assist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,389 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.

Model	Per session	Once invoked
Fable 5.1	$0.00096	$0.01389
Opus 5.5	$0.00038	$0.00556
Sonnet 5.5	$0.00019	$0.00278
Haiku 4.5	$0.00010	$0.00139

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

Security

Grade A, and why

landmark-navigation-assist 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.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/buildCallTask.js, scripts/locationConfigSchema.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/landmark-navigation-assist/SKILL.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose: Turns a pre-written, building-level location config into a CALL-E task instruction that guides a delivery driver (or repeat ride-hailing pickup) through the last few hundred meters to a specific building, using landmarks instead of GPS/text directions. Built for addresses where map pins and postal text routinely fail — landmark-based, informally-numbered, or newly-built areas — and the driver's own support call would otherwise be the fallback.

Not an address-reader. It's a guided conversation: the agent asks which direction the driver is approaching from, gives turn-by-turn landmark instructions for that direction, confirms the building by its distinguishing features, and only offers a human escalation contact if the driver is still stuck after being guided.

Key Features

Config-driven, not hardcoded. One JSON config per physical building (see references/location-config.schema.json), authored once and reused for every delivery to that address — this is what makes the skill reusable across locations rather than a one-off script for a single address.
Direction-aware disambiguation. The config supports multiple approach_from entries; the agent asks the driver which landmark they recognize and picks the matching guidance, rather than reading one fixed set of directions regardless of where the driver actually is.
In-call escalation only, driver-confirmed. If the driver is still stuck after being guided, the agent offers a human contact number — it never escalates automatically, and escalation resolves entirely within the same call (the agent reads the number aloud, the driver dials it themselves after hanging up). No webhook, no second outbound call, no SMS.
Structured result, not free-text parsing. Pairs with CALL-E's resultSchema to return escalation_offered, escalation_number_revealed, and resolution_summary as typed fields instead of requiring you to parse a transcript.

When to Use

Read the full file on GitHub · 90 lines

Files

What ships with it

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

1mo ago First seen · 90 lines · 96 tokens per session scan A 742b9b683572

Subscribe to this mod's changes

landmark-navigation-assist is a skill published in the GitHub repository CALLE-AI/awesome-phone-call-agents (109 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 1,389 once invoked, about $0.0004 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-09-15.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…