pr-to-lint-rule
Pass
Audited by Gen Agent Trust Hub on Sep 24, 2026
Risk Level: SAFEINDIRECT_PROMPT_INJECTIONCOMMAND_EXECUTIONEXTERNAL_DOWNLOADSDATA_EXFILTRATION
Full Analysis
- [INDIRECT_PROMPT_INJECTION]: The skills ingest untrusted input from users and repository content to perform tasks like lint rule generation.
- Ingestion points: The
$ARGUMENTSplaceholder inSKILL.mdand repository files read by theReadtool. - Boundary markers: Structured output contracts using
vigiles:okandvigiles:errblocks are used to isolate results. - Capability inventory: Access to
Bash,Write, andEdittools for project maintenance. - Sanitization: The project uses a subagent railway pattern to validate implementation steps and normalize shell commands for safety checks.
- [COMMAND_EXECUTION]: Automated tasks such as linting and testing are performed via the
Bashtool. - Evidence:
ship-pr/SKILL.mdexecutesnpm run lintandnpm testto verify code quality before opening a pull request. - [EXTERNAL_DOWNLOADS]: The testing harness utilizes well-known Docker images for isolated database testing.
- Evidence:
harness/measure-with-service.mjspulls thepostgres:16-alpineimage to verify database migrations. - [DATA_EXFILTRATION]: Egress monitoring is implemented to track and block unauthorized network requests.
- Evidence:
harness/oh-my-claudecode-egress.harness.mjsrecords update checks toregistry.npmjs.org, which is documented as a neutral finding for a well-known service.
Audit Metadata