[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7540RPG97YX5S2MV39JWYVQ":3,"skill-same:01M7540RPG97YX5S2MV39JWYVQ":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7540RPG97YX5S2MV39JWYVQ","drupal-security-review",null,"This skill should be used when the user asks to \"run a Drupal security review\", \"audit custom modules for security issues\", \"check for Drupal security vulnerabilities\", requests a security review of web\u002Fmodules\u002Fcustom or web\u002Fthemes\u002Fcustom, or before merging PRs that touch access control, forms, or data handling in this repository.","miteshmap\u002Fai","miteshmap","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2466013?v=4","01M753ZYJT8Y0GYGRB95KPX3N5","Mitesh Patel","01M753ZYKXH9ZBV3QYP4JQPKGF",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmiteshmap\u002Fai\u002Fblob\u002Fmain\u002Fskills\u002Fdrupal-security-review\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: drupal-security-review\ndescription: This skill should be used when the user asks to \"run a Drupal security review\", \"audit custom modules for security issues\", \"check for Drupal security vulnerabilities\", requests a security review of web\u002Fmodules\u002Fcustom or web\u002Fthemes\u002Fcustom, or before merging PRs that touch access control, forms, or data handling in this repository.\nlicense: MIT\n---\n\nTo perform a Drupal security review, audit this repository's custom code\nagainst the checklist below, which is derived from\nhttps:\u002F\u002Fwww.drupal.org\u002Fdocs\u002Fadministering-a-drupal-site\u002Fsecurity-in-drupal.\nOnly report issues in project code (custom modules\u002Fthemes, settings.php,\nconfig), not Drupal core or third-party contrib modules unless they have been\npatched locally. See `references\u002Fproject-modules.md` for this repository's\ncustom module\u002Ftheme scope paths and which modules to pay particular\nattention to for specific checklist items.\n\n## Review process\n\n1. Load `references\u002Fproject-modules.md` to get the custom module\u002Ftheme scope\n   paths and the per-checklist-item module hints for this repository.\n2. Default to a diff-based review: identify the changed files (e.g. from the\n   current PR\u002Fbranch diff or currently staged\u002Funstaged changes) that fall\n   under the custom module\u002Ftheme scope paths. Only run a full audit of the\n   entire custom module\u002Ftheme tree when explicitly asked for a full audit.\n3. Walk the checklist below section by section. For each item, search the\n   relevant code paths (PHP controllers\u002Fforms\u002Fservices, `.twig` templates,\n   `.js`, `.yml` permissions\u002Frouting, `settings.php`) for violations, using\n   the module hints from `references\u002Fproject-modules.md` to prioritize where\n   to look first.\n4. Skip sections that are not applicable (e.g. CAPTCHA\u002FPCI sections only\n   apply if that functionality exists in the code).\n5. Report only real findings with file:line evidence — do not speculate.\n\n## Checklist (from drupal.org \"Security in Drupal\")\n\n### Writing secure code for Drupal\n- **XSS \u002F output sanitization**: Twig templates rely on autoescaping — flag\n  any use of the `|raw` filter, `{{ content|raw }}`, or `#markup`\u002F`#allowed_tags`\n  render arrays built from unsanitized user input. Flag `class={{ class }}`\n  style unquoted Twig attributes (must be quoted).\n- Flag use of `check_markup()` outside a text-format context.\n- In JS, flag direct DOM insertion of user-controlled strings without\n  `Drupal.checkPlain()` \u002F equivalent escaping.\n- **SQL injection**: flag any `\\Database::getConnection()->query()` or\n  `db_query()` call with string-concatenated variables instead of named\n  placeholders (`:name`) or the query builder (`->condition()`, `->select()`).\n  Flag `LIKE` conditions missing `$connection->escapeLike()`. Flag user input\n  used as a query *operator* instead of a value.\n- **CSRF**: flag routes that perform state-changing actions (not just forms)\n  without `_csrf_token: 'true'` access checks in `*.routing.yml`.\n- Flag use of `t()`\u002Fplaceholders where `@variable`, `%variable`, `:variable`\n  are misapplied (e.g. `%variable` for a URL, `:variable` for arbitrary HTML).\n\n### Security of generated PHP files\n- Flag code that writes\u002Fgenerates `.php` files (e.g. via `file_put_contents`)\n  into web-accessible directories, or disables Drupal's protections for the\n  `php\u002Ftwig` compiled-template\u002Fcache directories.\n\n### Secure configuration for site builders\n- Review `*.permissions.yml` and route\u002Fentity access callbacks for overly\n  broad permissions (e.g. custom permissions granted to `authenticated user`\n  that should be restricted), and missing access checks on new routes\u002Fforms.\n- Flag debug\u002Fdevelopment settings left enabled for production (e.g.\n  `error_level` set to display errors, Twig `debug`\u002F`auto_reload` on) in\n  `settings.php` \u002F `sites\u002F*\u002Fsettings*.php`.\n\n### Preventing execution of untrusted PHP\n- Flag any use of the `php_eval`\u002FPHP filter format, `eval()`, `create_function()`,\n  or unserializing untrusted input (`unserialize()` on request data — prefer\n  JSON).\n\n### Securing authentication credentials\n- Flag API keys, tokens, or passwords hardcoded in custom module PHP, JS, or\n  committed config (`.yml`) instead of `settings.php`\u002Fenvironment variables\u002F\n  Key module. See `references\u002Fproject-modules.md` for which integrations to\n  check in particular for hardcoded secrets.\n- Scan the exported config in `.\u002Fconfig` (all `*.yml` files) for committed\n  secrets: API keys, client secrets\u002Fids, tokens, passwords, private keys, or\n  SMTP\u002Fwebhook credentials sitting directly in config values instead of being\n  referenced via the Key module or environment\u002F`settings.php` overrides. See\n  `references\u002Fproject-modules.md` for which config prefixes to pay\n  particular attention to.\n\n### Auditing config export for security-relevant permissions\n- Cross-check `.\u002Fconfig\u002Fuser.role.*.yml` and `.\u002Fconfig\u002F*.permissions` entries\n  against the \"Secure configuration for site builders\" guidance: flag broad\n  permissions (e.g. \"administer site configuration\", \"access administration\n  pages\", \"bypass node access\") granted to non-admin roles.\n- Flag exported text-format config (`.\u002Fconfig\u002Ffilter.format.*.yml`) that\n  grants a filtered\u002Funtrusted role access to the PHP filter or full HTML\n  without appropriate restriction (see \"Configuring text formats for\n  security\").\n\n### Securing file permissions and ownership\n- Flag custom code that changes file permissions to world-writable, or\n  writes uploaded files without validating extension\u002Fmime type via Drupal's\n  File API validators.\n\n### Session management\n- Flag custom code that alters session\u002Fcookie lifetime, `session.cookie_secure`,\n  or bypasses Drupal's session handling insecurely.\n\n### Password management\n- Flag custom login\u002Fregistration\u002Fpassword-reset code that stores passwords in\n  plain text, logs passwords, or implements custom hashing instead of using\n  Drupal's `PasswordInterface` service. See `references\u002Fproject-modules.md`\n  for which modules to check in particular.\n\n### Privacy management \u002F access bypass\n- Flag custom access logic that doesn't account for the \"deleting users who\n  authored content can lead to access bypass\" issue — e.g. custom node\u002Fentity\n  access callbacks keyed only on `uid` without checking current permissions.\n- Flag PII (emails, phone numbers, addresses) logged via `\\Drupal::logger()`\n  or exposed in custom REST\u002FJSON endpoints without access control. See\n  `references\u002Fproject-modules.md` for which endpoints to check in\n  particular.\n\n### Securing your site \u002F admin super user\n- Flag code that grants `uid: 1`-equivalent bypass-access shortcuts, or\n  custom permission checks using `->hasPermission('administer site\n  configuration')` where a narrower permission would do.\n- Flag hidden debug\u002Fadmin routes without permission or access requirements\n  in `*.routing.yml`.\n\n### Hiding Drupal version \u002F information disclosure\n- Flag custom code that exposes stack traces, `phpinfo()`, or verbose error\n  output to anonymous users.\n\n## Output format\n\nPresent findings as a table:\n\n| # | Severity | File | Lines | Issue | Checklist item |\n|---|----------|------|-------|-------|-----------------|\n\nSeverities: 🔴 CRITICAL, 🟠 HIGH, 🟡 MEDIUM, ⚪ LOW.\nEnd with a short summary of checklist sections reviewed and any that were\nskipped as not applicable.\n\n## Additional Resources\n\n### Reference Files\n\n- **`references\u002Fproject-modules.md`** - This repository's custom module\u002Ftheme\n  scope paths and which modules to prioritize for each checklist item.\n","To perform a Drupal security review, audit this repository's custom code\nagainst the checklist below, which is derived from\nhttps:\u002F\u002Fwww.drupal.org\u002Fdocs\u002Fadministering-a-drupal-site\u002Fsecurity-in-drupal.\nOnly report issues in project code (custom modules\u002Fthemes, settings.php,\nconfig), not Drupal core or third-party contrib modules unless they have been\npatched locally. See `references\u002Fproject-modules.md` for this repository's\ncustom module\u002Ftheme scope paths and which modules to pay particular\nattention to for specific checklist items.\n\n## Review process\n\n1. Load `references\u002Fproject-modules.md` to get the custom module\u002Ftheme scope\n   paths and the per-checklist-item module hints for this repository.\n2. Default to a diff-based review: identify the changed files (e.g. from the\n   current PR\u002Fbranch diff or currently staged\u002Funstaged changes) that fall\n   under the custom module\u002Ftheme scope paths. Only run a full audit of the\n   entire custom module\u002Ftheme tree when explicitly asked for a full audit.\n3. Walk the checklist below section by section. For each item, search the\n   relevant code paths (PHP controllers\u002Fforms\u002Fservices, `.twig` templates,\n   `.js`, `.yml` permissions\u002Frouting, `settings.php`) for violations, using\n   the module hints from `references\u002Fproject-modules.md` to prioritize where\n   to look first.\n4. Skip sections that are not applicable (e.g. CAPTCHA\u002FPCI sections only\n   apply if that functionality exists in the code).\n5. Report only real findings with file:line evidence — do not speculate.\n\n## Checklist (from drupal.org \"Security in Drupal\")\n\n### Writing secure code for Drupal\n- **XSS \u002F output sanitization**: Twig templates rely on autoescaping — flag\n  any use of the `|raw` filter, `{{ content|raw }}`, or `#markup`\u002F`#allowed_tags`\n  render arrays built from unsanitized user input. Flag `class={{ class }}`\n  style unquoted Twig attributes (must be quoted).\n- Flag use of `check_markup()` outside a text-format context.\n- In JS, flag direct DOM insertion of user-controlled strings without\n  `Drupal.checkPlain()` \u002F equivalent escaping.\n- **SQL injection**: flag any `\\Database::getConnection()->query()` or\n  `db_query()` call with string-concatenated variables instead of named\n  placeholders (`:name`) or the query builder (`->condition()`, `->select()`).\n  Flag `LIKE` conditions missing `$connection->escapeLike()`. Flag user input\n  used as a query *operator* instead of a value.\n- **CSRF**: flag routes that perform state-changing actions (not just forms)\n  without `_csrf_token: 'true'` access checks in `*.routing.yml`.\n- Flag use of `t()`\u002Fplaceholders where `@variable`, `%variable`, `:variable`\n  are misapplied (e.g. `%variable` for a URL, `:variable` for arbitrary HTML).\n\n### Security of generated PHP files\n- Flag code that writes\u002Fgenerates `.php` files (e.g. via `file_put_contents`)\n  into web-accessible directories, or disables Drupal's protections for the\n  `php\u002Ftwig` compiled-template\u002Fcache directories.\n\n### Secure configuration for site builders\n- Review `*.permissions.yml` and route\u002Fentity access callbacks for overly\n  broad permissions (e.g. custom permissions granted to `authenticated user`\n  that should be restricted), and missing access checks on new routes\u002Fforms.\n- Flag debug\u002Fdevelopment settings left enabled for production (e.g.\n  `error_level` set to display errors, Twig `debug`\u002F`auto_reload` on) in\n  `settings.php` \u002F `sites\u002F*\u002Fsettings*.php`.\n\n### Preventing execution of untrusted PHP\n- Flag any use of the `php_eval`\u002FPHP filter format, `eval()`, `create_function()`,\n  or unserializing untrusted input (`unserialize()` on request data — prefer\n  JSON).\n\n### Securing authentication credentials\n- Flag API keys, tokens, or passwords hardcoded in custom module PHP, JS, or\n  committed config (`.yml`) instead of `settings.php`\u002Fenvironment variables\u002F\n  Key module. See `references\u002Fproject-modules.md` for which integrations to\n  check in particular for hardcoded secrets.\n- Scan the exported config in `.\u002Fconfig` (all `*.yml` files) for committed\n  secrets: API keys, client secrets\u002Fids, tokens, passwords, private keys, or\n  SMTP\u002Fwebhook credentials sitting directly in config values instead of being\n  referenced via the Key module or environment\u002F`settings.php` overrides. See\n  `references\u002Fproject-modules.md` for which config prefixes to pay\n  particular attention to.\n\n### Auditing config export for security-relevant permissions\n- Cross-check `.\u002Fconfig\u002Fuser.role.*.yml` and `.\u002Fconfig\u002F*.permissions` entries\n  against the \"Secure configuration for site builders\" guidance: flag broad\n  permissions (e.g. \"administer site configuration\", \"access administration\n  pages\", \"bypass node access\") granted to non-admin roles.\n- Flag exported text-format config (`.\u002Fconfig\u002Ffilter.format.*.yml`) that\n  grants a filtered\u002Funtrusted role access to the PHP filter or full HTML\n  without appropriate restriction (see \"Configuring text formats for\n  security\").\n\n### Securing file permissions and ownership\n- Flag custom code that changes file permissions to world-writable, or\n  writes uploaded files without validating extension\u002Fmime type via Drupal's\n  File API validators.\n\n### Session management\n- Flag custom code that alters session\u002Fcookie lifetime, `session.cookie_secure`,\n  or bypasses Drupal's session handling insecurely.\n\n### Password management\n- Flag custom login\u002Fregistration\u002Fpassword-reset code that stores passwords in\n  plain text, logs passwords, or implements custom hashing instead of using\n  Drupal's `PasswordInterface` service. See `references\u002Fproject-modules.md`\n  for which modules to check in particular.\n\n### Privacy management \u002F access bypass\n- Flag custom access logic that doesn't account for the \"deleting users who\n  authored content can lead to access bypass\" issue — e.g. custom node\u002Fentity\n  access callbacks keyed only on `uid` without checking current permissions.\n- Flag PII (emails, phone numbers, addresses) logged via `\\Drupal::logger()`\n  or exposed in custom REST\u002FJSON endpoints without access control. See\n  `references\u002Fproject-modules.md` for which endpoints to check in\n  particular.\n\n### Securing your site \u002F admin super user\n- Flag code that grants `uid: 1`-equivalent bypass-access shortcuts, or\n  custom permission checks using `->hasPermission('administer site\n  configuration')` where a narrower permission would do.\n- Flag hidden debug\u002Fadmin routes without permission or access requirements\n  in `*.routing.yml`.\n\n### Hiding Drupal version \u002F information disclosure\n- Flag custom code that exposes stack traces, `phpinfo()`, or verbose error\n  output to anonymous users.\n\n## Output format\n\nPresent findings as a table:\n\n| # | Severity | File | Lines | Issue | Checklist item |\n|---|----------|------|-------|-------|-----------------|\n\nSeverities: 🔴 CRITICAL, 🟠 HIGH, 🟡 MEDIUM, ⚪ LOW.\nEnd with a short summary of checklist sections reviewed and any that were\nskipped as not applicable.\n\n## Additional Resources\n\n### Reference Files\n\n- **`references\u002Fproject-modules.md`** - This repository's custom module\u002Ftheme\n  scope paths and which modules to prioritize for each checklist item.\n",{"name":5,"license":15,"description":7},"main","61ef96fa5d1fec2e0c52d41ec0deae159fe0f0ed","skills\u002Fdrupal-security-review","https:\u002F\u002Fgithub.com\u002Fmiteshmap\u002Fai","https:\u002F\u002Fgithub.com\u002Fmiteshmap","https:\u002F\u002Fmitesh.dev","Software Engineer","2026-10-15 01:25:45",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add miteshmap\u002Fai --skill drupal-security-review",{"tool":38,"command":39},"bunx","bunx skills add miteshmap\u002Fai --skill drupal-security-review",{"tool":41,"command":42},"pnpm","pnpm dlx skills add miteshmap\u002Fai --skill drupal-security-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmiteshmap\u002Fai\u002Fblob\u002Fmain\u002Fskills\u002Fdrupal-security-review\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fproject-modules.md","REFERENCE","参考文档",1467,"https:\u002F\u002Fgithub.com\u002Fmiteshmap\u002Fai\u002Fblob\u002Fmain\u002Fskills\u002Fdrupal-security-review\u002Freferences\u002Fproject-modules.md",[53],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":58,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M75419PBX7RVXRHF78TXTTHN","figma","Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmiteshmap\u002Fai\u002Fblob\u002Fmain\u002Fskills\u002Ffigma\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmiteshmap\u002Fai\u002Fblob\u002Fmain\u002Fskills\u002Ffigma\u002FSKILL.md",[],[]]