A Security Benchmark for Claude Code Agent Skills
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 42/100. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
Claude Code
Model
Claude
Fastest way to find out if MaliciousAgentSkillsBench belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/protectskills/MaliciousAgentSkillsBench ~/.claude/skills/maliciousagentskillsbenchRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/skills/maliciousagentskillsbenchNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ skills/ │ └─ maliciousagentskillsbench/ ← installs here ├─ agents/ └─ settings.json
A Security Benchmark for Claude Code Agent Skills
Source: GitHub repository
Source check: July 19, 2026
Upstream commit: July 8, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.