ai-embeddings
Pass
Audited by Gen Agent Trust Hub on Jun 13, 2026
Risk Level: SAFECOMMAND_EXECUTIONDATA_EXFILTRATIONPROMPT_INJECTION
Full Analysis
- [COMMAND_EXECUTION]: Insecure deserialization pattern detected using the
picklelibrary. - Evidence: The skill provides examples of using
pickle.load(f)andpickle.dump()to manage document metadata associated with vector indices inreferences/vector-indexing.mdandreferences/embedding-training.md. - Risk: If an attacker provides a malicious
.docsfile, loading it withpicklecan lead to arbitrary code execution. This is a common pattern in machine learning utilities but remains a security concern when handling untrusted data. - [DATA_EXFILTRATION]: Functional network operations to well-known service providers.
- Evidence: Integration with OpenAI and Cohere APIs for generating embeddings as documented in
references/embedding-api-integration.mdandreferences/embedding-models.md. - Context: These operations are consistent with the skill's primary purpose and use well-known, trusted domains (api.openai.com, api.cohere.com).
- [PROMPT_INJECTION]: Indirect prompt injection vulnerability surface.
- Ingestion points: The skill is designed to ingest and process large volumes of untrusted text data via functions like
embed_pipeline,fixed_size_chunks, andsemantic_chunksinSKILL.mdandreferences/chunking-strategies.md. - Boundary markers: While the protocol suggests stripping HTML/Markdown, it lacks robust delimiter enforcement or instructions to the agent to ignore prompt-like content within the ingested documents.
- Capability inventory: The skill possesses the ability to write to the local filesystem (indexing/caching) and make outbound network requests (API embedding services).
- Sanitization: There is no evidence of sanitization to prevent adversarial instructions embedded in processed documents from influencing the agent's behavior during the embedding or retrieval phases.
Audit Metadata