Topic starter
02/08/2026 11:35 am
TL;DR: Claude Skills introduces a package-like supply chain for AI agents, and researchers cited by Akto found 36.82% of skills contain security flaws while a separate analysis of 42,447 skills found 26.1% carry at least one vulnerability. The security gap is no longer theoretical: agent skills can spread silently, inherit broad runtime access, and evade conventional scanning.
Editorial analysis by NHI Mgmt Group, based on content published by Akto: “5 Claude Agent Skills Risks Every CISO Should Know”.
By the numbers:
- 36.82% of skills contain security flaws, according to researchers cited by Akto.
- One audit discovered 400+ agent skills on workstations that the security team had no idea existed, according to Akto.
- A documented campaign flooded a major registry with 1,184 malicious skills across 12 publisher accounts, according to Akto.
Key questions
Q: What breaks when agent skills are added without central governance?
A: Security teams lose visibility into what has been installed, who approved it, and which runtime context it can reach.
Q: Why do inherited permissions make agent skills risky?
A: Because the skill often operates with the agent's existing context rather than its own scoped identity.
Q: What do security teams get wrong when reviewing agent skills for enterprise use?
A: The most common mistake is judging a skill by its wording rather than by its operational scope.
Practitioner guidance
- Establish a central skill inventory Map every Claude Skill, agent extension and imported capability across developer workstations, cloud sandboxes and SaaS agents so security teams can see what is installed, where it runs and who approved it.
- Enforce per-skill privilege boundaries Restrict each skill to the minimum filesystem, network and API scope required for its task, and block inherited access to cloud credentials or database connections unless explicitly approved.
- Scan for markdown-based payloads Inspect SKILL.md content, load-time commands and linked registries for hidden instructions, external fetches and secret access patterns that conventional code scanning will miss.
Bottom line: Claude Skills exposes a governance gap where agent extensions behave like a supply chain, yet many organisations still lack inventory, provenance and runtime boundaries for them.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:48 pm
Agent skills are becoming a governed supply chain, not a prompt convenience. Once capability is modular and portable, the security question shifts from whether the model is safe to whether the surrounding artifact ecosystem is trusted. That places provenance, inventory and version control at the centre of agent governance. Practitioners should stop treating skills as disposable extensions and manage them as controlled runtime dependencies.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
- Patching addresses only about 10% of privilege escalation techniques, while privilege management covers about 65%, according to Verizon's 2026 Data Breach Investigations Report.
A question worth separating out:
Q: How should teams respond when a harmful skill is discovered in production?
A: Contain the skill first, then rotate any credentials or tokens it could have accessed and check for propagation across other registries or platforms. Because skills are portable, response has to cover every environment that imported the same capability, not only the workstation where it was first found.
👉 Read our full editorial: Claude Skills security risks expose a new agentic supply chain