amazon-location-service

A development guide for Amazon Location Service, a cloud service that adds maps and location functions to applications. Geocoding converts addresses into coordinates, while routing finds travel paths.

In plain words
What is it for?
It helps add maps, place search, geocoding, routing, geofencing, and tracking to applications using Amazon Location Service.
Why use it?
It explains the setup and integration work needed for location features, including authentication and software-library use.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add aws-geospatial/amazon-location-agent-context
agentmods
npx agentmods add plugins/aws-geospatial/amazon-location-agent-context/amazon-location-service
Clone the repo
git clone --depth 1 https://github.com/aws-geospatial/amazon-location-agent-context

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Security

Grade A, and why

amazon-location-service 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 2d 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.

Origin

This is a copy

100% identical to amazon-location-service — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/amazon-location-service/.claude-plugin/plugin.json · 24 lines

What it actually says

{
  "author": {
    "name": "Amazon Web Services"
  },
  "description": "Guide developers through adding maps, places search, geocoding, routing, and other geospatial features with Amazon Location Service, including authentication setup, SDK integration, and best practices",
  "keywords": [
    "location",
    "maps",
    "geocoding",
    "routing",
    "places",
    "geofencing",
    "tracking",
    "amazon-location",
    "maplibre",
    "address",
    "coordinates"
  ],
  "license": "Apache-2.0",
  "name": "amazon-location-service",
  "repository": "https://github.com/awslabs/agent-plugins",
  "version": "1.1.0"
}
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. 2d ago First seen · 24 lines scan A 81407914f4cd

Subscribe to this mod's changes

amazon-location-service is a plugin published in the GitHub repository aws-geospatial/amazon-location-agent-context (6 stars, last pushed 5d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 100% identical to amazon-location-service, differing in 4 lines, and is treated as a copy.