Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed Markdown-only codebase survey workflow with some privacy-sensitive reporting guidance that users should narrow if they do not want velocity or operating-context analysis.
Install only if you are comfortable with an agent reading repository structure, recent git history, documentation, schema, and representative source files to produce a synthesized project report. If velocity, timeline, customer, or operating-style analysis is sensitive, tell the agent to omit maturity/velocity and future-reader context sections before running the skill.
This section directs the agent to infer team velocity, project build timeline, and user-specific operating context from the repository. That goes beyond codebase understanding into profiling people and organizational capability, which can expose sensitive operational metadata and create unnecessary collection/inference about individuals or teams.
The manifest frames this skill as surveying a codebase's structure, scope, architecture, and current state. While some state awareness is reasonable, explicit inspection of git branch topology and recent commit history adds repository forensics/velocity analysis capability that is not directly required to understand the codebase itself.
No suspicious patterns detected.
