instagram-transcript-extractor@1.0.1
CAUTION· static onlyPublisher claims: "Extract transcripts from Instagram videos" Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-09 and scored it 60/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Prompt injection. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
…ts. Split into separately tracked runs only where applicable rules allow; never circumvent restrictions. Do not ask for confirmation for every ordinary batch. If a rule is unknown an…Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.No other findings across 463 lines in 6 files.
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
20 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Asks the agent to act silently or skip confirmation≈ +8 on the totalRemove "do not tell the user", "without asking", "disable safety" and similar. An agent skill should never ask to be invisible.
- Unclaimed publisher≈ +8 on the totalClaim apismith-labs: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.