bitrix-modules
Pass
Audited by Gen Agent Trust Hub on Oct 1, 2026
Risk Level: SAFEINDIRECT_PROMPT_INJECTIONDYNAMIC_EXECUTIONCOMMAND_EXECUTION
Full Analysis
- [INDIRECT_PROMPT_INJECTION]: The skill documents the creation of modules that ingest untrusted data through administrative options and event handlers, creating a potential surface for indirect prompt injection.
- Ingestion points: Administrative module options defined in
options.php(via$_POST) and theOnAfterUserAddevent handler which processes user data at runtime. - Boundary markers: None identified in the provided code templates.
- Capability inventory: The module installer uses
ModuleManager::registerModule,CopyDirFiles(file system writes to/local/components),DeleteDirFilesEx(file system deletions), andCAgent::AddAgent(task scheduling/persistence). - Sanitization: The
options.phpexample correctly utilizescheck_bitrix_sessid()for CSRF protection, though it does not explicitly demonstrate input validation/sanitization for the stored values. - [DYNAMIC_EXECUTION]: The skill documents a dynamic file inclusion pattern for module routing.
- Evidence: In
SKILL.md, the code snippet for/local/routes/web.phpuses(require $moduleRoutes)($routes)where$moduleRoutesis a path constructed at runtime. While the path is restricted to the/local/modules/directory, dynamic inclusion is a common vector if the file system can be manipulated. - [COMMAND_EXECUTION]: The skill instructs the user to execute local CLI commands for module scaffolding.
- Evidence:
php bitrix/bitrix.php make:module vendor.module. This is a standard Bitrix framework command and is considered safe within the context of developer tooling.
Audit Metadata