Topic starter
18/08/2026 2:09 pm
TL;DR: Agent skills written in markdown can vary at runtime, hide unsafe code, and slip past review when sourced from third parties, so IBM Research and Alice are targeting the problem with Mellea and Caterpillar, according to ActiveFence. The real issue is not just code quality but governable trust in machine-generated instructions that now behave like non-human identity inputs.
Editorial analysis by NHI Mgmt Group, based on content published by ActiveFence: “Securing Agent Skills Before They Run”.
Key questions
Q: What breaks when third-party agent skills are not governed like privileged inputs?
A: When agent skills are treated as harmless content, organisations miss the fact that those instructions can steer tools, secrets, and execution paths.
Q: Why do AI agent skills create supply chain risk in enterprise environments?
A: AI agent skills create supply chain risk because they can look harmless in review while delivering malicious behavior only when executed.
Q: What are the signs that an agent skill is failing governance checks?
A: Look for unexpected external network calls, credential access, obfuscated logic, broad permission requests, or behaviour that changes materially between runs.
Practitioner guidance
- Establish a third-party skill intake gate Require provenance checks, ownership review, and risk classification before any external agent skill can enter a production repository or agent catalogue.
- Compile high-trust skills into typed contracts Use structured execution artefacts with explicit inputs, outputs, and policy hooks for workflows that can touch sensitive data or tools.
- Scan skills for supply-chain abuse patterns Detect credential theft, external callbacks, persistence mechanisms, code obfuscation, and remote script execution before runtime.
Bottom line: Third-party agent skills can hide unsafe behaviour, making them a supply-chain risk rather than a harmless prompt file.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
18/08/2026 3:02 pm
Agent skills are becoming an AI supply-chain control point, not a content format. Once a skill can influence execution, the governance model has to treat it like a software artifact with provenance, policy, and runtime restrictions. That changes the boundary for AI programmes because review must happen before an agent ever interprets the instructions. The practitioner conclusion is simple: if the skill can change system behaviour, it belongs in the software supply-chain review process.
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.
A question worth separating out:
Q: How should teams govern third-party skills in agent ecosystems?
A: Treat third-party skills as privileged dependencies, not harmless add-ons. Require ownership, source review, and explicit approval before a skill can inherit access to data or tools, and revoke that access when the skill’s purpose, provenance, or maintenance status is no longer clear.
👉 Read our full editorial: Securing agent skills before they become an AI supply-chain risk