Yesterday a new release landed for Mova, a context governance tool, and the scope just got a lot sharper. The creator, a Redditor posting as u/1982_miguel, stopped trying to build a general-purpose tool. Instead the focus narrowed to one job: auditing the context that gets sent to an LLM, right before it leaves your environment. One job, done well, beats ten jobs done halfway. That focus is exactly what makes this release worth a look.
Most teams bolt safety checks onto the output side. They wait for the model to respond, then scan what came back for anything ugly. Mova flips that order. It sits right before inference and checks the payload on its way out the door. That happens before you spend a single token generating a response you might have to throw away anyway.
Here is what actually changed in this release. The new egress_audit config block sits right before egress and answers 11 basic audit questions about the payload. Does it contain PII, does it leak secrets, does it break your policy rules, what will the token count and estimated cost look like. It pulls those answers from logs and trace evidence instead of asking you to guess.
The twist is the dry-run mode. You can sanitize and audit a payload without ever invoking the LLM at all. That means you can test an entire pipeline and catch a leaked API key or a policy violation, and never spend a token finding out. One commenter on the thread flagged exactly why this matters: most guardrail tools only look at what the model said after it already ran. Mova checks what you were about to send, before you pay for the privilege of finding out it was a bad idea.
The author also cleaned house this round. Legacy TUI code and unused dependencies are gone, which shrinks the binary down. The test setup got simplified into three runnable examples. The README got rewritten to be straightforward instead of exhaustive. Small changes, but the kind that make a tool easier to actually adopt instead of just admire.
Here is the mini-workflow if you want to try it:
- 🔍 Pull the repo and skim the three example test cases first. See the shape of a real audit run before you touch your own config.
- ⚙️ Add the egress_audit block to your config, pointed at the context you are about to ship to the model.
- 🧪 Flip on dry-run mode first. Sanitize and audit without touching the LLM, so you are not burning tokens on a config you have not trusted yet.
- Read through all 11 audit answers one by one: PII, secrets, policy rules, token count, cost. Do not skim past the ones that look boring.
- 🛡️ Once the dry run comes back clean, turn dry-run off. Let it run for real, right before egress, on every request.
Pro tip: run dry-run mode as a CI step, not just a local sanity check before you push. If a teammate’s prompt template starts leaking a customer email address into context, you want that caught in a pull request. Not in production logs three weeks later.
Pro tip: the token count and cost estimate baked into the 11-question audit is worth watching, even if you do not care about PII. A context block that silently balloons in size is usually a sign something upstream is duplicating data. This is a cheap way to catch that before your API bill does.
One thing worth being upfront about: this Redditor flagged it clearly in the post, and I appreciate that kind of honesty. PII masking here runs on heuristics, not on a legal compliance guarantee. It catches obvious patterns and sloppy leaks. It will not replace a real compliance review if you are shipping something regulated. Do not mistake a clean audit for a signed-off legal document.
Compared to most guardrail setups, this one is different. Most sit after the model responds and try to catch a bad output. This one sits before the call and tries to stop a bad input from going out at all. Different layer, different failure mode. Honestly, it is a layer most people skip, because they only think about safety on the way back in.
If you run a pipeline that shoves a lot of context at an LLM, this is worth a look. RAG systems, agents pulling from logs, anything touching customer data, all fit the case. Check out the README and the examples before your next deploy. If you hit an edge case, this project’s creator is actively asking for feedback on the repo. 🚀
Frequently Asked Questions
Q: Why audit context before sending it to the LLM?
Most people think about guardrails after the model responds, but pre-inference auditing catches sensitive data, secrets, and policy violations before they leave your environment. It’s like checking your pockets before boarding a flight, prevention beats recovery.
Q: What’s the dry-run mode for?
Dry-run mode sanitizes and audits your context without calling the LLM, so you can test audit rules and see what gets flagged without burning tokens. It’s perfect for iterating on your setup before going live.
Q: Can I rely on Mova’s PII masking for compliance?
Mova’s PII detection is heuristics-based, not legally bulletproof. Think of it as a helpful security layer, not a complete guarantee. For production, pair it with other safeguards.
Q: How do I get started?
The README walks you through the 11 audit questions and core concepts. Check out the three runnable examples to see it in action, pick one, clone the repo, and customize from there.
New release for Mova: focused on pre-inference context governance and auditing
by u/1982_miguel in PromptEngineering