Загрузка видео...

Не удалось загрузить видео

На главную

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 просмотров • 10 дней назад •via X (Twitter)

Комментарии: 39

Фото профиля Marouane Lamharzi Alaoui
Marouane Lamharzi Alaoui10 дней назад

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 | ⴰⴽⵉⵜⴰⵔ
Akitar | ⴰⴽⵉⵜⴰⵔ10 дней назад

Great work! We need to educate AI about Morocco

Фото профиля Marouane Lamharzi Alaoui
Marouane Lamharzi Alaoui10 дней назад

Fixed

Фото профиля Hamza
Hamza10 дней назад

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

Фото профиля Zack
Zack10 дней назад

Promo video b opus nadia

Фото профиля Dr. Abdelhak El Mansour
Dr. Abdelhak El Mansour10 дней назад

Amazing job a wzzoun

Фото профиля Abdou
Abdou10 дней назад

Did you try using it in geoguessr?

Фото профиля Marouane Lamharzi Alaoui
Marouane Lamharzi Alaoui10 дней назад

Aced it

Фото профиля Kaito | 海斗
Kaito | 海斗10 дней назад

BRO THIS IS MAD

Фото профиля Idriss Douelfiqar
Idriss Douelfiqar10 дней назад

can u please check this picture

Фото профиля Marouane Lamharzi Alaoui
Marouane Lamharzi Alaoui10 дней назад

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

Фото профиля Idriss Douelfiqar
Idriss Douelfiqar10 дней назад

holly shhiiit! exactly at this point

Фото профиля Makarov Le Grand ! ✠
Makarov Le Grand ! ✠10 дней назад

Impressive , palantir's calling !

Фото профиля MiklaS
MiklaS10 дней назад

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
Decentralize_010 дней назад

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

Фото профиля Driss Nafii
Driss Nafii10 дней назад

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

Фото профиля Max
Max10 дней назад

OSINTers are cooked

Фото профиля Daniel Johnsen
Daniel Johnsen10 дней назад

geoguessr players in shambles lol

Фото профиля Ysf
Ysf10 дней назад

m9wd

Фото профиля catman
catman10 дней назад

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
Omar10 дней назад

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
Morgan10 дней назад

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

Фото профиля Caio Pizzol
Caio Pizzol10 дней назад

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

Фото профиля waz mazighael
waz mazighael10 дней назад

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

Фото профиля Simon Lo
Simon Lo10 дней назад

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
Marouane Lamharzi Alaoui10 дней назад

You get a full evidence dossier

Фото профиля Ibliss
Ibliss10 дней назад

wooow amazing work

Фото профиля Soufiane Jarrah سفيان جراح
Soufiane Jarrah سفيان جراح10 дней назад

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

Фото профиля som
som10 дней назад

Amazing, how much time did it take to build ?

Фото профиля FBS
FBS10 дней назад

Next level

Фото профиля Ayoub Arbouchi
Ayoub Arbouchi10 дней назад

Samaritan :v

Фото профиля Kolyn
Kolyn10 дней назад

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

Фото профиля Josh Builds
Josh Builds10 дней назад

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

Фото профиля DEX
DEX10 дней назад

clean

Фото профиля Freak 🔺
Freak 🔺10 дней назад

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
DARKKEVN Labs10 дней назад

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

Фото профиля Brkani
Brkani10 дней назад

👌

Фото профиля 𝒜𝖑-𝕭𝖆𝖙𝖗𝖔𝖘ⴰⵍⴱⴰⵟⵔⵓⵙ
𝒜𝖑-𝕭𝖆𝖙𝖗𝖔𝖘ⴰⵍⴱⴰⵟⵔⵓⵙ10 дней назад

👍👏👏👏

Фото профиля Costa
Costa10 дней назад

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?

Похожие видео

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 просмотров • 4 месяцев назад

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 просмотров • 3 месяцев назад

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 просмотров • 3 месяцев назад