findmy

findmy is a command for coding agents from omarshahine/findmy-cli. It costs 27 tokens per session (478 once invoked), scanned A, original, MIT.

A command that reads friend locations from Find My on macOS using on-screen text recognition. It can report a person's name, location, distance, and how recently the location was updated.

In plain words
What is it for?
Use it to list all visible friends or look up one person by name, including their location, distance, and location-update status.
Why use it?
It provides location details from the Find My app without requiring you to inspect the app manually. It also distinguishes live locations from paused or older last-known locations.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the openclaw-findmy plugin — 1 skill, 1 command shipped together

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.

agentmods
npx agentmods add commands/omarshahine/findmy-cli/findmy
Clone the repo
git clone --depth 1 https://github.com/omarshahine/findmy-cli

Or install openclaw-findmy, the plugin that ships this one along with the rest of its 1 skill, 1 command.

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 findmy

README.md
[![agentmods](https://agentmods.dev/badge/commands/omarshahine/findmy-cli/findmy.svg)](https://agentmods.dev/commands/omarshahine/findmy-cli/findmy)
Your own site
<a href="https://agentmods.dev/commands/omarshahine/findmy-cli/findmy"><img src="https://agentmods.dev/badge/commands/omarshahine/findmy-cli/findmy.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 478 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00027 $0.00478
Opus 5 $0.00014 $0.00239
Sonnet 5 $0.00005 $0.00096
Haiku 4.5 $0.00003 $0.00048

Measured 4d ago against content hash 8820f51ece32, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

findmy 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 4d 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.

commands/findmy.md · 48 lines

What it actually says

/findmy — Where is everyone?

Query Find My via the bundled findmy CLI. With no arguments, returns every friend in the FindMy.app People sidebar. With a name argument, returns just that friend (case-insensitive substring match).

Run

If $ARGUMENTS is empty:

"${CLAUDE_PLUGIN_ROOT}/scripts/findmy.sh" people --json

Otherwise:

"${CLAUDE_PLUGIN_ROOT}/scripts/findmy.sh" person "$ARGUMENTS" --json

How to report results to the user

  • Lead with the friend's name, location, and distance when known.
  • If staleness is "Paused", say so up front — the location is the last known position, not live. Example: "Omar paused location sharing; last known position was Redmond, WA (7 mi away)."
  • If staleness is a time string like "5 min. ago", mention it inline: "Omar is in Redmond, WA — updated 5 min ago."
  • If staleness is empty/missing, treat the location as live.
  • For multi-person output, sort by name and present as a short list.
  • For person <name> lookups that return "no person matching", say so plainly and offer to list everyone with /findmy (no args).

Caveats to surface only when relevant

  • This raises FindMy.app to the front briefly during the lookup.
  • On a headless Mac, the display must be awake (the CLI nudges it via caffeinate -u, but a real or dummy USB-C display must be attached).
  • Two /findmy invocations within ~5s can fail with "could not create image from window" — wait a few seconds and retry.
  • The CLI reads UI text, not coordinates. No lat/lon is available.
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. 4d ago First seen · 48 lines · 27 tokens per session scan A 8820f51ece32

Subscribe to this mod's changes

findmy is a command published in the GitHub repository omarshahine/findmy-cli (54 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 478 once invoked, about $0.0001 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.