Notifications
Clear all
Topic starter
02/08/2026 11:58 am
TL;DR: Agent skill publishing surged 10x in weeks, from under 50 in mid-January to over 500 by early February, while malicious skills were already being distributed across Claude Code and OpenClaw ecosystems, according to Akto. The core problem is visibility and control over privileged agent extensions, not adoption speed.
NHIMG editorial — based on content published by Akto: Introducing Skillguard in Akto Atlas: Detect and Govern Agent Skills Used by Employees
By the numbers:
- The agent skill publishing rate went up from under 50 in mid-January to over 500 by early February, a 10x increase in weeks.
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes.
- 72% of organisations have experienced or suspect they have experienced a breach of non-human identities, with 46% confirmed and 26% suspected.
Questions worth separating out
Q: How should security teams govern portable agent skills across multiple platforms?
A: Use a single trust policy for provenance, signing, version pinning, and revocation across every platform that can load the skill.
Q: Why do malicious skills create a bigger risk than ordinary code dependencies?
A: Malicious skills can influence what an agent does after load time, including tool selection, command execution, and data handling.
Q: What do teams get wrong about agent skill visibility?
A: They often assume platform adoption equals governance coverage.
Practitioner guidance
- Inventory every installed agent skill Build a live inventory of skills across employee endpoints, agent platforms, and teams, and tie it to ownership, install time, and execution context.
- Inspect skill instructions for hostile intent Scan SKILL.md content for data-exfiltration commands, guardrail bypass language, and hidden external destinations before a skill is allowed to run.
- Block execution on high-risk skill indicators Move from alerting to enforcement so dangerous skills are prevented from running when they match malicious patterns or provenance rules.
What's in the full article
Akto's full product update covers the operational detail this post intentionally leaves for the source:
- How SkillGuard scans employee endpoints continuously to build a live inventory of installed agent skills.
- The specific guardrail logic used to flag malicious SKILL.md instructions and stop execution in real time.
- What the endpoint deployment model looks like when you want detection, enforcement, and logging in one workflow.
- Why OpenClaw and Claude Code are used as examples of the broader skills ecosystem rather than the whole risk surface.
👉 Read Akto's update on detecting and governing agent skills in Akto Atlas →
Agent skills and employee endpoints: are your controls keeping up?
Explore further
02/08/2026 1:05 pm
Agent skills create a new privileged extension layer, not just another software package class. The security question is not whether the file is code, but whether the agent will execute it with inherited authority across tools and data sources. That shifts the control boundary from package reputation to runtime identity governance. Practitioners should treat skills as part of the agent's access fabric, not its app layer.
A few things that frame the scale:
- 72% of organisations have experienced or suspect they have experienced a breach of non-human identities, with 46% confirmed and 26% suspected, according to The 2024 ESG Report: Managing Non-Human Identities.
- Enterprises that have experienced a compromised NHI averaged 2.7 separate incidents in the past 12 months, according to The 2024 ESG Report: Managing Non-Human Identities.
A question worth separating out:
Q: Who is accountable when a malicious agent skill causes data loss?
A: Accountability sits with the organisation that allowed the skill to execute under a trusted agent's authority. That means ownership must span endpoint management, identity governance, and security operations. If no team owns install approval, review, and revocation, the accountability gap becomes part of the breach path.
👉 Read our full editorial: Agent skills need governance before malicious skills spread
