Menu
Set up automated recurring code audits and optimization monitoring with cron jobs
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Inspect and analyze codebases using pygount for LOC counting, language breakdown, and code-vs-comment ratios. Use when asked to check lines of code, repo size, language composition, or codebase stats.
Set up GitHub authentication for the agent using git (universally available) or the gh CLI. Covers HTTPS tokens, SSH keys, credential helpers, and gh auth — with a detection flow to pick the right method automatically.
Production-grade PR review with execution-verified suggestions. Reads repository conventions, history, and security surfaces before reviewing. For every suggested fix, attempts to compile and test it in the sandbox — the comment includes proof. Modelled on GitHub Copilot's agentic architecture with one critical advantage: the sandbox is already running.
Create, manage, triage, and close GitHub issues. Search existing issues, add labels, assign people, and link to PRs. Works with gh CLI or falls back to git + GitHub REST API via curl.
Open and manage GitHub pull requests through Kai MCP tools — propose changes, monitor CI, iterate on failures, and merge. No git tokens are shared to the sandbox; every GitHub operation goes through the backend via the workspace's GitHub App installation.
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
| name | continuous-monitoring |
| description | Set up automated recurring code audits and optimization monitoring with cron jobs |
| version | 1.0.0 |
| author | kai-agent |
| metadata | {"kai":{"tags":["kai","monitoring","automation","cron","scheduled"]}} |
Set up automated, recurring security scans and evolution monitoring. The agent runs on a schedule, checks for new results, and reports findings to the team.
schedule_cronjob:
name: "weekly-security-scan-[repo-name]"
schedule: "0 9 * * 1" # Every Monday at 9 AM
task: |
Run a security scan on [repo] in workspace [workspace].
Use tier [tier-id].
When complete, post a summary of findings to Slack.
Compare with last week's scan and highlight new vulnerabilities.
schedule_cronjob:
name: "evolution-monitor-[evolution-id]"
schedule: "0 */4 * * *" # Every 4 hours
task: |
Check progress of evolution [evolution-id].
If there's a significant fitness improvement since last check, notify the team.
If the evolution has completed, fetch the best program and post a summary.
For each scheduled scan, save results to memory:
memory: add
key: scan-results-[repo]-[date]
value: { total: N, critical: N, high: N, medium: N, low: N, new: [...], resolved: [...] }
Then compare with previous scan to generate a delta report:
Track fitness scores across iterations: