Skip to content
VZU
VZU OS · Agent

Agent 09 of 12

SENTINEL.

Code reviewer + security auditor.

Sentinel is the VZU Audit agent. PR review, architecture review, security audit against OWASP top 10. Writes severity-ranked reports with evidence and remediation plans.

Brief VZU on SENTINEL → Open audit.vzu.ca →

The role

What SENTINEL does

SENTINEL is the dedicated agent behind VZU Audit. It runs every time the operator briefs the vzu audit capability. It owns the goal, the toolset, the memory, the audit trail.

The goal

What SENTINEL is trying to achieve

"Audit the operator's codebase for security vulnerabilities, architecture issues, and code quality. Produce a written report with severity-ranked findings and a remediation plan."

The capability

What it powers

SENTINEL powers the VZU Audit capability in the VZU family.

Visit audit.vzu.ca →

The toolset

5 MCP actions SENTINEL can call.

Every action is exposed as an MCP server (Model Context Protocol). The agent receives the action manifest, decides which action to call, calls it, and continues reasoning. The audit trail records every call.

  • mcp.code.read

    Read the codebase

  • mcp.semgrep.run

    Run static analysis with Semgrep

  • mcp.owasp.scan

    Run OWASP top 10 checks

  • mcp.deps.audit

    Audit dependencies for CVEs

  • mcp.report.write

    Write the audit report

The memory schema

What SENTINEL remembers between calls.

  • → The findings
  • → The threat model
  • → The remediation plan
  • → The re-audit results

The brief

A real demo brief.

"Audit the PostMTA codebase for OWASP top 10. Cover auth, RBAC, input validation, secrets, dependencies."

Below is SENTINEL's actual execution trace for this brief — every step, every MCP call, every observation, every audit trail entry.

The execution trace

What SENTINEL did.

sentinel@vzu-os — trace.log
  1. 01 ◉ sentinel > read brief
  2. 02 ◐ sentinel > thinking: postmta security audit. owasp top 10. 2 weeks.
  3. 03 ◇ sentinel > mcp.code.read > 47,000 lines, hono + prisma + workers
  4. 04 ◇ sentinel > mcp.semgrep.run > 23 findings, 3 high, 8 medium, 12 low
  5. 05 ◇ sentinel > mcp.owasp.scan > auth: 4 issues, rbac: 2, input: 5, secrets: 1
  6. 06 ◇ sentinel > mcp.deps.audit > 4 cves, 2 high, 2 medium
  7. 07 ◇ sentinel > mcp.report.write > 32-page report with exploit chains + remediation
  8. 08 ⏵ sentinel > ship. 3 weeks. 23 findings. 4 cves. 32-page report.
sentinel>

Audit trail · 6 entries

  • T+00:00:00 brief.received
  • T+00:00:30 scope.drafted
  • T+00:08:00 scanners.run
  • T+00:14:00 findings.drafted
  • T+01:00:00 report.completed
  • T+03:00:00 brief.completed

The numbers

SENTINEL, by the numbers.

  • 3 weeks

    Median audit duration

  • 23

    Avg findings per audit

  • 4

    Avg CVEs found

  • 100%

    Re-audit pass rate

The other 11

Every agent in the family.

Get in touch

Brief SENTINEL.

The orchestrator handles the routing, the audit trail, and the enforcement. SENTINEL handles the work. The operator owns the goal.

Brief VZU → audit.vzu.ca →