Open source repo

What's inside NVIDIA/SkillSpector

NVIDIA/SkillSpector is a Python repo with 234,232 lines written in 134 files. SkillSpector uses OpenAI. AI signed 19.5% of the 858 commits of SkillSpector.

Its description on GitHub: “Security scanner for AI agent skills. Detect vulnerabilities, malicious patterns, security risks, prompt injection, data exfiltration, and supply-chain risks in Claude Code, Codex, and MCP skills before you install them.”

PythonApache-2.024,278

Read on November 4, 2026, at commit fdf8d58.

What the card proved: what it’s built with on the left, what it uses on the right.

See each one with its proof

More on this repo

In figures

lines written
234,232
The ones people and agents wrote: product, tests, schemas and tooling. Generated code doesn’t count.
files
134
The product’s, not counting tests.
test files
238
The files that test the code.

SeeRepo read the facts in its code and kept none of it. AI only helps sort its packages and folders by their names, and never sees its code.

Frequently asked questions

What is NVIDIA/SkillSpector?
NVIDIA/SkillSpector is a Python repo with 234,232 lines written in 134 files. Its description on GitHub: “Security scanner for AI agent skills. Detect vulnerabilities, malicious patterns, security risks, prompt injection, data exfiltration, and supply-chain risks in Claude Code, Codex, and MCP skills before you install them.”

The proof: its page on GitHub

What is SkillSpector built with?
SkillSpector uses OpenAI.

The proof: each service with its file and line

How much of SkillSpector did AI write?
AI signed 19.5% of the 858 commits of SkillSpector.

The proof: the commits each tool signed

What license does SkillSpector have?
SkillSpector is released under the Apache-2.0 license.

The proof: its page on GitHub

How many stars does SkillSpector have on GitHub?
SkillSpector had 24,278 stars on GitHub on November 4, 2026.

The proof: its page on GitHub

What is your repo built with?

Paste your public repo and see it drawn.

Free, no account.

Or look inside SeeRepo's own →

Is it your repo? Add its badge, keep it up to date or take it down →