Examine a repository
Nine agents. Evidence for every finding. Runs in your browser.
Connections
Optional
GitHub
Cerberus account
Repository write access is separate from account sign-in.
Signing in stores your GitHub ID, username, and verified primary email for your Cerberus account. Sessions expire after seven days. Privacy details
Use a token for repository scans
No token stored. Token is kept in this tab only.
Pollinations
AI analysis
Use an API key instead
Recent Scans
Examining your repository
- 01 Read repository
- 02 Evaluate checks
- 03 Build report
Waking the pack
resolving target
AGENT INITIALIZED // SWARM STANDBY
ORCHESTRATOR SWARM TELEMETRY
0%
LIVE CHECK LOG
Suggested Pull Request
Catalog-based examples to adapt and test
Repository-backed change set
Connect GitHub repository access to let the agent inspect files and prepare a reviewable patch.
CHECK AN ADAPTED PATCH LOCALLY (GIT CLI)
git apply --check patch.diff
Proposed Code Diffs
+ added lines · − removed lines · numbers are new-file line numbers · click a file header to expand
Agent Engineering Plan
Findings, observations, and follow-up work derived from this scan.
CURATED AGENT LOOP PROMPT
Security Scorecard
-
Agent Swarm Profile
Clean
Watch
High failure rate
All Checks
AI Analyst Report
Agent console
Welcome back.
Repository workspace
Proposed changes
Generate a reviewed patch to see code here while you talk with the agent.
Recent agent work
No repository-backed changes yet.
Preparing your scan report…
Examination complete. Organizing recorded findings, coverage, and follow-up notes for review.