Authorization notice. Geo Sleuth is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Remote script. The install command fetches and runs the skill from GitHub, so review the repo before installing on a machine with sensitive files.
Reverse engineering. The skill can pinpoint where a person was photographed, so use it only on photos you have the right to analyze and do not use it to track individuals.
Who it is forAn OSINT researcher or journalist holding a photo with stripped EXIF data who needs its location for a story or check.
The problemA photo with no sign, plate or landmark gives no obvious clue, and manual search across maps and terrain takes hours.
The outcomeThe agent returns the camera position with an error radius, the direction the camera faced, a satellite evidence image and a graded confidence.
What you need first
- An agent that reads SKILL.md and can run shell commands (the README names Claude Code, Codex, Cursor, Gemini CLI, OpenCode and GitHub Copilot)
- Python, since the scripts are written in Python
- Node.js with npx, to run the install command (inferred from the npx install line)
- Network access for OpenStreetMap data, elevation data, satellite tiles and street view, as the README describes
- The photo to locate, with EXIF data preferably stripped or absent as in the README cases
Steps
- Run
npx skills add Oldcircle/geo-sleuthand pick your agents when prompted. - Ask the agent to run doctor.py from the installed skill's scripts/ folder and fix any failed checks. (inferred, check the README)
- Hand the agent the photo and say: find where this photo was taken.
- Read the returned coordinates, error radius, heading and evidence image.
- Open the evidence image and check that the named files and commands from the session support the conclusion.
Prompt for your agent
Use the geo-sleuth skill from the Oldcircle/geo-sleuth repo to find where <path to photo> was taken. Expect a camera position with an error radius, a heading, a satellite evidence image and a confidence grade. Verify that the conclusion names the commands run and the files they produced.
Caveat. The README's cases are single runs by one model, and the README says a different model or different choices may not reach the same result.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page