Agent Orchestration
Spawns specialised sub-agents, fans them out in parallel and synthesises the results.
Cybersecurity · Application Development
I work where offensive security meets software engineering — from recon and red teaming to tools people actually want to use.
I live in cybersecurity and write the software to go with it. That means I hunt for weaknesses, rebuild attack chains end to end, and understand systems deeply enough to harden them again — and whatever real engagements are missing tends to turn into a small, focused tool.
My long-term project: an autonomous assistant that doesn't just answer — it acts. It plans work, spawns its own agents to fan out across a problem, builds and ships software, and runs security work from recon to a finished report. This is what it looks like in motion:
Spawns specialised sub-agents, fans them out in parallel and synthesises the results.
Maps the target, finds vulnerabilities, verifies them and writes them up cleanly.
Plans attack chains and runs them in an isolated lab, aligned to MITRE ATT&CK.
From prototype to a tested, deployable tool — code, tests, CI, release.
Systematically surfaces infrastructure, certificates and leaked secrets.
Builds containers, wires up the reverse proxy and TLS, keeps an eye on health.
Public tools, all in Python. Small, focused, built for the command line.
Paste a requirements.txt or a package.json. Every package is
checked live against the OSV.dev
database for known vulnerabilities. Runs server-side, nothing is stored.
requirements.txt, package.json or a whole
.zip project here —
Files are parsed in memory, never executed. Archives are scanned with strict limits.