Agent Orchestration
Spawns specialised sub-agents, fans them out in parallel and synthesises the results.
Cybersecurity · Application Development
building & securing software
↑ this terminal is live — click it and type help
I work in cybersecurity and build the software to go with it. I care about systems that are well made and hard to break — and the small, sharp tools that get me there.
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, and builds and ships
software on its own. Type agents in the terminal to watch it orchestrate.
Spawns specialised sub-agents, fans them out in parallel and synthesises the results.
Reviews systems and dependencies for weaknesses and helps close them.
From prototype to a tested, deployable tool — code, tests, CI, release.
Turns repetitive, fiddly work into small, reliable tools.
Learns new topics on its own and turns them into lasting knowledge.
Builds containers, wires up the reverse proxy and TLS, keeps an eye on health.
A messenger that hides more than the message. Traffic runs through a real mix network, so the operator of the service cannot tell who is talking to whom. Keys are hybrid post-quantum, so today's recorded traffic stays useless tomorrow.
Three layers of mix nodes plus providers, Sphinx packets and cover traffic. Timing and routing metadata go with it.
Hybrid key agreement, classical and lattice based side by side. Harvest now, decrypt later does not pay off.
Messages are encrypted on the device. The server only ever stores ciphertext it cannot read.
Encrypted voice and video over WebRTC, with an own TURN server for peers behind strict NAT.
Whole stack in containers: app, database, mix nodes, relay. No third party in the path.
A PWA, not an app store detour. Works in the browser, pins to the home screen.
Public tools, all in Python. Small, focused, built for the command line. Type projects to list them in the terminal.
Paste a requirements.txt or a package.json — or drop a whole project.
Every package is checked live against the
OSV.dev database for known
vulnerabilities. Runs server-side, nothing is stored, nothing is executed.
requirements.txt, package.json or a whole
.zip project here —
Files are parsed in memory, never executed. Archives are scanned with strict limits.