OpenOSINT
AI-powered OSINT agent with interactive REPL, MCP server, and CLI. 20 tools. Works with Claude, GPT-4, or local models. For authorized security research only.
Runssource: GitHubhomepagePythonMITcommit a0a525376c38
Python, MIT licensed. The project labels itself: ai agent, anthropic, claude, cli, cybersecurity, holehe, llm and maigret.
OpenOSINT runs. An Argusic agent installed it in 12 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
OpenOSINT 2.29.0 installs from source, CLI shows help with 20 tools, DNS tool resolves real domains, playbook generates real investigation reports, web server serves on port 9877 with HTTP 200 on / and /api/health, and 712 automated tests pass.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Wrong sherlock package installed (distributed locking library sherlock != sherlock-project)3 minutes
- sublist3r binary not found (search_domain tool) causing one test assertion failure2 minutes
- holehe and sherlock-project not installed causing 2 person-playbook test failures2 minutes
- Install time
- 12 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pytest tests/ -> 712 passed, 26 skipped, 0 failed; uvicorn openosint.web_server:create_app --factory --port 9877 -> curl http://127.0.0.1:9877/ = 200 (78629 bytes); /api/health = 200 {"status":"ok","version":"2.29.0"}; openosint dns example.com = real DNS records; openosint playbook domain example.com = report file written
- Model tokens used
- 72,324
- Exact commit tested
- a0a525376c38
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
"msg": "holehe and sherlock-project not installed causing 2 person-playbook test failures",
"fix": "pip install holehe sherlock-project",
"minutes": 2
}
],
"test_depth": "tier1_real",
"notes": "Verified against real internet: DNS lookup on example.com returned A/AAAA/NS/MX/TXT/DMA…
"verified_how": "pytest tests/ -> 712 passed, 26 skipped, 0 failed; uvicorn openosint.web_server:…
"final_state": "OpenOSINT 2.29.0 installs from source, CLI shows help with 20 tools, DNS tool res…
}
tokens used
72,324Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 12 minutes to install, slower than the median of the 24 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 25 ai-agent projects Argusic has installed and timed, OpenOSINT was the 19th fastest to reach a running state, and 17 of 25 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
ai-agentanthropicclaudeclicybersecurityholehellmmaigretmcpmcp-servermodel-context-protocolosintosint-toolspythonreconnaissancesecuritysherlockterminalthreat-intelligence
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openosint)Questions
- Does OpenOSINT run?
- Yes. OpenOSINT runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test OpenOSINT?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a0a525376c38. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test OpenOSINT?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does OpenOSINT take to install?
- 12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does OpenOSINT need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing OpenOSINT?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does OpenOSINT compare with the alternatives?
- Of the 25 ai-agent projects Argusic has installed and timed, OpenOSINT was the 19th fastest to reach a running state, and 17 of 25 reached one at all.
- Where is the evidence for OpenOSINT?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.