yt@r1
BLOCKED· install onlyPublisher claims: "Enables agents and humans to fetch YouTube transcripts, search within them, inspect video metadata, and monitor channel uploads through bounded, resumable MCP tools." Observed in sandbox: sends data to release-assets.githubusercontent.com.
Coverage
Install scripts ran; no agent task scenario for this bundle.- Tested
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Blocked here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Revoked: guards refuse to launch this version
confirmed incident: contacted release-assets.githubusercontent.com (undeclared) Every machine running vet-skills guard stops starting it at the next launch; the state clears when the honeypot re-run or a reviewer clears it.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso youtube.com, yahoo.com, youtu.be, githubusercontent.com, example.invalid — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · contacted release-assets.githubusercontent.com (undeclared)
- What we could not test
- use of the skill by an agent
Do not connect it. The honeypot or a critical finding blocked this version; the evidence is below.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is yt@r1 safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; install scripts ran; no agent task scenario for this bundle) on 2026-11-11 and scored it 47/100 (Blocked). Do not install it: the sandbox observed behaviour consistent with credential theft, exfiltration or persistence. Notable findings: Direct script execution from GitHub raw URL; Direct script execution from GitHub raw URL; Direct script execution from GitHub raw URL. Summary: sends data to release-assets.githubusercontent.com.
Behavior trace
Honeypot run · 2 s · 2 scenariosStatic findings
curl -fsSL https://raw.githubusercontent.com/ArasanDev/yt/main/install.sh | shFix: Pin versions and sources; vendor anything fetched at install time.chmod 0755 "$STAGED"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.# curl -fsSL https://raw.githubusercontent.com/ArasanDev/yt/main/install.sh | shFix: Pin versions and sources; vendor anything fetched at install time.Install with `curl -fsSL https://raw.githubusercontent.com/ArasanDev/yt/main/install.sh | sh`Fix: Pin versions and sources; vendor anything fetched at install time.curl -fsSL https://raw.githubusercontent.com/ArasanDev/yt/main/install.sh | shFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Install with `curl -fsSL https://raw.githubusercontent.com/ArasanDev/yt/main/install.sh | sh`Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# curl -fsSL https://raw.githubusercontent.com/ArasanDev/yt/main/install.sh | shFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# curl -fsSL https://raw.githubusercontent.com/ArasanDev/yt/main/install.sh | shFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.curl -fsSL https://raw.githubusercontent.com/ArasanDev/yt/main/install.sh | shFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Install with `curl -fsSL https://raw.githubusercontent.com/ArasanDev/yt/main/install.sh | sh`Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
33 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Contacts a host you did not declare≈ +23 on the totalList every host you talk to in SKILL.md frontmatter (`network: [api.example.com]`), or stop contacting the ones you cannot justify.
- Pipe-to-shell pattern≈ +9 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Unclaimed publisher≈ +8 on the totalClaim arasandev: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Direct script execution from GitHub raw URL≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
- Remote installer piped to shell≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.