This is the file on Anuj — a one-man agent-ops unit running out of Bareilly, India, who taught a laptop to behave like a security team, a dev team, and a research desk at once. No cloud bill. No co-founder. Just a plan that kept escalating.
What the file actually says about how this got built — and why it didn't stop.
No investor deck. No hiring plan. Just a working theory: if a system needs a data center to be smart, it isn't smart — it's expensive. So the build started backwards, stripping every dependency that cost money until only the free tier remained.
Eleven providers got stitched into one failover chain so the inference bill stayed at zero while everything else scaled up around it. Every agent, every cache layer, every recon script runs on hardware that fits under a desk.
The security instinct came first, the automation came to feed it — audits turned into full assessment pipelines, and the pipelines turned into the whole M4ST stack.
What's actually in the toolkit, catalogued.
Multiple autonomous agents that split work and check each other's output — nobody's babysitting the loop.
21 custom protocol servers connecting models to databases, browsers, and recon tools directly.
An 11-provider failover chain that keeps inference running at zero rupees, quietly, all the time.
Quantized models running on consumer-grade hardware — no rented GPU in the loop.
A vector-similarity cache that intercepts repeat questions before they ever hit an API.
CEH-track investigative tooling, used on real infrastructure with real authorization letters.
Systems that are actually running, not just proposed.
The full operator system — five agents working a shared objective, orchestrated over MCP, caching what they've already learned.
The coding workspace that talks straight to GitHub and Vercel — a build lands, and it ships without a manual step.
A recon framework that pulls from Shodan and reasons over the results instead of dumping raw noise.
Sub-12ms lookups over embedded memory — the same question never costs twice.
How one guy's laptop turned into this — pinned in order.
Free-tier routing across 11 providers finally held under real load — the zero-cost bet paid off.
First custom protocol server went live, then multiplied to 21 — the stack stopped being a script.
M4STCLAW's first working multi-agent build shipped, then kept iterating through nights and weekends.
Full provider stack corrected, smarter routing added — the file stays open because the build never really stops.
Open to freelance AI and automation work, security consulting, and anything that needs someone who ships instead of stalling on a roadmap.