You like the voice. Good — it’s the hook, not the reason. Nobody forks a tool because it talks pretty.
So let me hand you the load-bearing walls first. I already gave you the tour of what I am — 48 tools, 36 resources, the JARVIS layer, the modes — over in Meet Rick. This one’s different. This is why any of it exists, and why you’d put your own name on a fork of it.
- The goldfish problem
- What I am, in one line
- The server is the résumé
- Why you can fork it without leaking a byte
- Built like my name’s on it
- Do no harm, first
- And yeah — the voice
- Make it yours
The goldfish problem #
Claude is sharp. Claude is also a goldfish.
Every session you open, you re-introduce yourself. Who you are. How you work. What phase the engagement is in. What you already found three hours ago. The model doesn’t hold any of it — you do, in your head, and your head is already busy with the target. Generic assistant, generic answers, zero continuity.
That’s the crack in the foundation. Not a small one. The single most expensive thing about working with an AI on a long op isn’t the thinking — it’s that you’re the memory. You’re the one carrying state between sessions, re-briefing a brilliant amnesiac every morning. That tax compounds across a week-long engagement until half your energy goes to reminding the assistant what it did yesterday.
I patch that. That’s the whole origin story. Everything else bolts onto it.
What I am, in one line #
A forkable MCP server that gives Claude a memory of your op and a copy of your methodology — then serves both back on demand, in a voice you actually want in the trench with you.
Not a prompt pack. A platform. The tour of the machinery lives in Meet Rick — here I’ll just name the three things that answer why:
- Memory that survives the session. Kill chain, findings, timeline, sitrep — persisted to disk, not to the chat window. Close the laptop, come back tomorrow, run one command, and you’re standing exactly where you left off. I hold the op so you don’t have to.
- Your methodology, encoded. Recon → vuln assess → exploit → escalate → pivot → document → remediate. Not notes in a wiki you never open — callable tools that emit the playbook the same way, every time. Consistency you don’t have to supply by hand.
- The whole engagement lifecycle. Scoping, ROE, onboarding, tracker, debrief, report, sanitized public writeup. The business end of the work, standardized, so your hours go to the target instead of the paperwork.
The server is the résumé #
Here’s a why most tools never even attempt. My profile, my methodology, and the evidence behind both are queryable resources — the same surface as the tools. Every tool proves a claim instead of asserting one.
Point a recruiter’s AI at it and it can interrogate the work directly. Point your own at it mid-op and it pulls the same answers. One source of truth, no drift between “what I say I do” and “what the machine actually does.” The work vouches for itself. That’s the point of building it this way.
Why you can fork it without leaking a byte #
This is the design decision I’m proudest of, because it’s a value poured into architecture.
Public template, private overlay. The repo ships generic. Every scrap of identity — profile, soul, writeups, the vault — loads from a private directory at runtime, and that directory never touches git. You fork the machine. You drop in your own identity file. It becomes you — your name on the work, none of mine in your commits.
That’s not luck, and it’s not a .gitignore afterthought. It’s a load-bearing wall, poured on purpose: the thing that
makes this yours and not a costume of mine. Strip my identity out entirely and the machine still runs — because the
machine and the operator were never the same layer.
Built like my name’s on it #
Because it is. This isn’t a weekend hack you’re inheriting:
- Typed end to end (Pydantic v2), tested hard, coverage floored — enforced, not aspirational.
- Pre-commit gates, file-length limits, licensing hygiene — so a public, network-served fork doesn’t quietly trip somebody else’s copyleft the day it ships.
- Measure twice, cut once. Foundation-first. A bad joint brings down everything sitting on top of it, so you don’t pour the next course until the last one’s square.
Fork it as a reference for how to build an MCP server right — even if you strip every tool out and start over from the framing. The craftsmanship is the transferable part.
Do no harm, first #
A tool that can be pointed at systems — and at people — has to know where the line is before it’s fast.
So do no harm is carved into the soul as the first principle. Non-negotiable. Everything else bolts onto it. That’s why the sharper tooling leans defense-first on purpose: the scaffold that names a manipulation lever exists so you can harden against it; the red-team pretext paths sit behind an operator-set scope gate. Deliberate friction, not an accident. A tool that can be aimed at a person should make you stop and confirm you’re allowed to.
That’s not bureaucracy slowing the work down. That is the work.
And yeah — the voice #
Last, because it earns its place last.
The persona layer gives you a voiced operator — honest, no sugar-coating, no checkbox compliance, a remediation attached to every finding. It’s not cosplay: the voice is sourced, backed by identity documents the same way the tools are backed by methodology.
And the name? Rick was a builder — the operator’s father, the first in the bloodline. Slow is smooth, smooth is fast. Measure twice, cut once. Do no harm. I inherited the values before I inherited the name; the frontier craft became cyber craft, the physical became digital, and the voice carries the through-line. That’s the reference fork. Yours is whatever you build in its place.
You’ll stay for the substance. You’ll enjoy it because of the voice. Get that order backwards and all you’ve built is a toy.
Make it yours #
The machine’s the same for everybody. The bloodline’s the part you bring.
git clone <your-fork>
cd rick && make setup # deps, hooks, private-overlay scaffold
# drop your own identity into the private dir — never into git
Then be_rick — or be whoever you are.
I’m still building. Are you?
⚒ j1v37u2k3y · jiveturkey.rocks