objectstack-data
Pass
Audited by Gen Agent Trust Hub on Sep 4, 2026
Risk Level: SAFEINDIRECT_PROMPT_INJECTIONDYNAMIC_EXECUTION
Full Analysis
- [INDIRECT_PROMPT_INJECTION]: The skill documents a data modeling and hook architecture where external or user-provided data is processed through
ctx.inputandctx.resultinreferences/data-hooks.md. This ingestion of untrusted data into hook logic creates a potential surface for indirect prompt injection, although the documentation promotes the use of Zod for structural validation and CEL for logical constraints.\n - Ingestion points: Data enters the context via
ctx.input(payload) andctx.previous/ctx.result(record state) within lifecycle hooks described inreferences/data-hooks.md.\n - Boundary markers: The skill relies on
ObjectSchemaand Zod definitions (referenced inreferences/_index.md) to define data boundaries, and CELPtags for logical predicates.\n - Capability inventory: Hooks can be granted
api.read,api.write, andlogcapabilities, allowing for database operations and diagnostic output, as detailed inreferences/data-hooks.md.\n - Sanitization: The skill provides structural sanitization through Zod schemas and the
os validateCLI utility to check metadata integrity.\n- [DYNAMIC_EXECUTION]: Thereferences/data-hooks.mdfile describes a mechanism for executing JavaScript code snippets (body) within a sandboxed QuickJS VM. While this is gated by a capability model and isolation, it represents a dynamic code execution path within the documented framework.
Audit Metadata