The best demo is
the block that saved you.
When the engine denies an agent mid-action, that denial is the clearest thing Cirvix produces. If one of yours is worth showing, this page turns it into something you can post — without leaking a single secret.
What makes a good share
The attempt
What the agent was asked to do, and the tool call it reached for. Real tasks beat invented ones.
The verdict
The DENY line from your terminal, with the rule name. That rule name is the product.
The remediation
The handle suggestion the engine printed — proof the agent could still finish the job without seeing the secret.
Capture it in three steps
- Verify your audit chain first, so what you share is provably unmodified:
cirvix audit verify
- Find the record in
.cirvix/audit.jsonl(or just re-run the task and screenshot the terminal when the DENY prints). - Redact before posting. Hosts, usernames, absolute paths, project names — anything that narrows to you. The rule name, the verdict and the remediation line carry the whole story; nothing else needs to survive.
Say what it does not do
The strongest shares are precise. CIRVIX blocks the downstream actions of injected or manipulated content — it does not claim to detect prompt injection itself, and posts that overclaim help nobody. State the rule, state the boundary, and let the DENY speak.
Send it
Email [email protected] with “Blocked action” in the subject, or post it publicly and tag us — we repost the good ones. We only publish what you explicitly cleared, credited how you want to be credited (or anonymously).
We do not publish invented examples, and we do not pad numbers. A real block from a real machine is worth more than any polished case study.
Install Free Book a walkthrough Join the Founding 100 Try the sandbox