Loading video...

Video Failed to Load

Go Home

I built GeoInt, an open-source skill for Codex and Claude Code that finds where any photo was taken, with proof. It reads every detail in the image, like signs, plates, buildings, plants and the light. It searches several reverse image engines, runs multiple vision models on your own machine,...

62,664 views • 9 days ago •via X (Twitter)

39 Comments

Marouane Lamharzi Alaoui's profile picture
Marouane Lamharzi Alaoui9 days ago

It's free and MIT-licensed: To install it, just ask Claude Code or Codex: "install the skill at It works best with Codex on GPT-6.1 Sol, and it's great in Claude Code with Opus too.

Akitar | ⴰⴽⵉⵜⴰⵔ's profile picture
Akitar | ⴰⴽⵉⵜⴰⵔ9 days ago

Great work! We need to educate AI about Morocco

Marouane Lamharzi Alaoui's profile picture
Marouane Lamharzi Alaoui9 days ago

Fixed

Hamza's profile picture
Hamza9 days ago

tested in a photo without GPS or EXIF, just the coastal rock and cliffside huts, It guessed it right ! Impressive work 👏

Zack's profile picture
Zack9 days ago

Promo video b opus nadia

Dr. Abdelhak El Mansour's profile picture
Dr. Abdelhak El Mansour9 days ago

Amazing job a wzzoun

Abdou's profile picture
Abdou9 days ago

Did you try using it in geoguessr?

Marouane Lamharzi Alaoui's profile picture
Marouane Lamharzi Alaoui9 days ago

Aced it

Kaito | 海斗's profile picture
Kaito | 海斗8 days ago

BRO THIS IS MAD

Idriss Douelfiqar's profile picture
Idriss Douelfiqar8 days ago

can u please check this picture

Marouane Lamharzi Alaoui's profile picture
Marouane Lamharzi Alaoui8 days ago

40°50'06.9"N 14°15'00.0"E

Idriss Douelfiqar's profile picture
Idriss Douelfiqar8 days ago

holly shhiiit! exactly at this point

Makarov Le Grand ! ✠'s profile picture
Makarov Le Grand ! ✠8 days ago

Impressive , palantir's calling !

MiklaS's profile picture
MiklaS9 days ago

i’m running your repo against the old travel dump i keep calling anonymized, and it’s making me rethink blur as privacy; you may have built a better red-team for my camera roll than for investigators

Decentralize_0's profile picture
Decentralize_09 days ago

Seriously...bravo 👏 Like wtf. Insane 🔥🔥🔥

Driss Nafii's profile picture
Driss Nafii8 days ago

L Front, nta li 9aditiha ? Backend I know, ms l front bzzaf diik l animation li fiha

Max's profile picture
Max9 days ago

OSINTers are cooked

Daniel Johnsen's profile picture
Daniel Johnsen9 days ago

geoguessr players in shambles lol

Ysf's profile picture
Ysf9 days ago

m9wd

catman's profile picture
catman9 days ago

Treating each clue like a witness is the right shape: one sign can mislead, but independent details that converge make the location much more defensible.

Omar's profile picture
Omar8 days ago

Did you try it in Geoguessr ? Not urban areas but some rural field in the middle of Brazil, Isaan (northeast thailand) and/or Philippines

Morgan's profile picture
Morgan9 days ago

how often does it get the exact street right, not just the city?

Caio Pizzol's profile picture
Caio Pizzol8 days ago

i created a read-video skill that pulls frames out of user bug videos. never thought to ask where they were filmed.

waz mazighael's profile picture
waz mazighael9 days ago

OSINTs used to collect big amounts of contributions just doing this work

Simon Lo's profile picture
Simon Lo9 days ago

wait does it tell you which clue actually nailed the location or just the final guess? that's the part I'd trust

Marouane Lamharzi Alaoui's profile picture
Marouane Lamharzi Alaoui9 days ago

You get a full evidence dossier

Ibliss's profile picture
Ibliss9 days ago

wooow amazing work

Soufiane Jarrah سفيان جراح's profile picture
Soufiane Jarrah سفيان جراح9 days ago

Maybe the G.R or The DGSN could be interested?

som's profile picture
som8 days ago

Amazing, how much time did it take to build ?

FBS's profile picture
FBS8 days ago

Next level

Ayoub Arbouchi's profile picture
Ayoub Arbouchi8 days ago

Samaritan :v

Kolyn's profile picture
Kolyn8 days ago

Dwi m3ana b darija, rah maghadich ijawbk tibo whya samm mamsalich

Josh Builds's profile picture
Josh Builds9 days ago

reading the plants and the light to place a photo is the part that feels like real detective work

DEX's profile picture
DEX8 days ago

clean

Freak 🔺's profile picture
Freak 🔺8 days ago

running the vision models locally is the smart call here. the photos people want located are exactly the ones you don't want leaving the machine. how long does a full run take?

DARKKEVN Labs's profile picture
DARKKEVN Labs8 days ago

Showing the evidence behind each guess is the best part, it makes the result something you can actually check.

Brkani's profile picture
Brkani9 days ago

👌

𝒜𝖑-𝕭𝖆𝖙𝖗𝖔𝖘ⴰⵍⴱⴰⵟⵔⵓⵙ's profile picture
𝒜𝖑-𝕭𝖆𝖙𝖗𝖔𝖘ⴰⵍⴱⴰⵟⵔⵓⵙ9 days ago

👍👏👏👏

Costa's profile picture
Costa8 days ago

wild tool, but it works both ways. same pipeline a stalker runs on someone's IG story does it flag when the photo itself is AI-generated, or will it confidently geolocate a street that doesn't exist?

Related Videos

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

56,568 views • 4 months ago

Someone ran Claude Code on a beach where any device overheats and that spot suddenly turned out to be the best home for the most powerful AI in the world. This is the reMarkable Paper Pro. A paper tablet for notes with no browser and no social media and not a single app. He sat down right on the sand in the open sun and brought up Claude Code on Opus 4.6 over the Claude API on the paper screen and opened his project ~/repos/webs while the waves broke a few steps away. For years every device had the same trouble outside. In direct sun the screen glares and washes out and heats up and instead of your work you see your own reflection. But e-ink does not blast its own light into your face. It reflects the sunlight like the page of a book. And here is what came out of it. The very thing that kills any normal screen outside turned into fuel for this one. The brighter the sun the sharper the picture because it has nothing to glare with and nothing to wash out. And then comes the thing no laptop on a beach will give you. Your eyes do not get tired. You can watch Opus think on max effort for an hour and it reads like a book in the sun and not a backlight you squint into. The picture only comes alive. In bright light it does not fade but turns sharper and higher in contrast than it ever was in a room. The charge lasts for days. E-ink barely touches the battery so there is no outlet anywhere on the sand and the tablet does not care. It weighs as much as a notebook. The whole setup folds into a beach bag like a pad with a pen on top. Everything on the screen is for real. Claude Code v2.1.110 and Opus 4.6 on the Claude API and the project ~/repos/webs open right on the e-ink in the middle of the sand. In my opinion this is the most unexpected home for an AI this year. Not an office with the blinds drawn and not a monitor cranked to full brightness but a quiet sheet of paper on the sand that open sun only makes better and on it the most powerful Claude writes code right on the page like a pen.

Blaze

89,713 views • 3 months ago

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

43,089 views • 3 months ago