Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed requirements and prototype assistant with optional local validation tools, and I found no hidden install, persistence, or data-exfiltration behavior.
Before installing, expect the skill to work with your local requirements, PRDs, prototypes, examples, and optionally validation scripts. Use the check/gate commands only on files you intend it to inspect, avoid including raw secrets in project artifacts, and independently verify any legal, medical, or domain-rule conclusions against current authoritative sources.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
Repository/CI validator wiring audits and filesystem scans that can block builds are materially different from a requirements/prototype assistant. Hidden CI/build-gate behavior is dangerous because it can influence delivery pipelines and inspect repository internals under a misleading label.
No suspicious patterns detected.
