Loading the registry…
Opt out of telemetry / tracking / error reporting / analytics / feedback uploads across every locally installed AI CLI and AI-enabled IDE — Anthropic Claude Code, OpenAI Codex CLI, Google Gemini CLI, GitHub CLI (gh) + Copilot CLI, Cursor, Cursor CLI (cursor-agent), Google Antigravity, VS Code (vscode), JetBrains PhpStorm — plus Vercel CLI and macOS + Windows OS-level privacy surfaces (Apple Intelligence, Mac Analytics, Advertising ID, Recall, Copilot, Diagnostic Data). Applies documented opt-out flags per vendor, diffs against live vendor docs to surface NEW vars not in baseline, and reports persistent local state without deleting anything. Triggers include "opt out", "opt out of telemetry", "disable telemetry", "disable tracking", "privacy mode", "kill switch", "disable analytics", "stop sending data", "ai cli opt out", "disable apple intelligence" — the full list is under "Trigger phrases" in the body, which is documentation, not discovery.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
37 critical findings reported by cisco-skill-scanner, 16 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- ai-cli-optout
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- ai-cli-optout ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.8s
v2.0.11
302 findings · 67.9s
v0.3.26
34 findings · 59.5s
v0.1.0
0 findings · 17.7s
v0.1.0
15 findings · 17.7s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image, nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 11, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 351 findings above stand exactly as their scanners reported them, at full severity.