glab-govern
Pass
Audited by Gen Agent Trust Hub on Oct 11, 2026
Risk Level: SAFECOMMAND_EXECUTIONDATA_EXFILTRATIONPERSISTENCEINDIRECT_PROMPT_INJECTION
Full Analysis
- [COMMAND_EXECUTION]: The skill instructs the agent to perform operations using the
glabCLI, specifically theglab governsubcommands for setup, diagnostics, and audit synchronization. - [DATA_EXFILTRATION]: The skill's primary function is to read local agent transcripts and send them to a GitLab instance as audit events using
glab govern audit sync. The documentation explicitly warns the user to treat transcript content as sensitive and to verify the target project and host before synchronization. - [PERSISTENCE]: The skill automates the configuration of persistence through the
glab govern setupcommand, which installsStopandSessionEndhooks in the~/.claude/settings.jsonfile. These hooks ensure that audit synchronization runs automatically at the end of agent turns or sessions. - [INDIRECT_PROMPT_INJECTION]: The skill creates an attack surface by ingesting and processing agent transcripts, which are dynamic and untrusted data sources.
- Ingestion points: Local agent transcript entries read by the
glab govern audit synccommand (as described inSKILL.mdandreferences/commands.md). - Boundary markers: The provided instructions do not specify any markers or delimiters to separate transcript content from audit metadata, though the underlying
glabtool may handle this. - Capability inventory: The skill uses the
glabCLI, which has capabilities for file system access (reading transcripts and settings) and network communication (GitLab API interaction). - Sanitization: The instructions do not mention explicit sanitization or filtering of the transcript data before it is sent to the GitLab audit logs.
Audit Metadata