agentmods.dev

deploy-check

A pre-deployment checklist for Drupal projects, covering configuration, dependencies, database updates, source control, code quality, and deployment scripts.

In plain words
What is it for?
Use it before deploying to verify project status, Composer files, database updates, Git state, custom-code warnings, and the order of deployment commands.
Why use it?
It finds common release blockers such as unexported configuration, missing lock files, security advisories, pending updates, uncommitted changes, and debug code.

Command

1 5mo ago A scan 24 tokens original MIT
View the source file abderrahimghazali/drupal-boost
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/abderrahimghazali/drupal-boost/deploy-check
Clone the repo
git clone --depth 1 https://github.com/abderrahimghazali/drupal-boost
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 518 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.00518
Opus 5 $0.00012 $0.00259
Sonnet 5 $0.00005 $0.00104
Haiku 4.5 $0.00002 $0.00052

Measured yesterday against content hash ad22a988659e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

deploy-check scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/deploy-check.md · 74 lines

What it actually says

Pre-Deployment Readiness Check

You are checking if this Drupal project is ready for deployment. Run through each check:

Check 1: Configuration Status

# Check for uncommitted config changes
drush config:status
  • If config is out of sync, warn the user to export and commit

Check 2: Composer Lock

  • Verify composer.lock exists and is committed
  • Run composer validate to check composer.json syntax
  • Check for security advisories: composer audit

Check 3: Database Updates

# Check for pending updates
drush updatedb --no-post-updates --no-cache-clear 2>&1 | head -20
  • If updates exist, they will run during deployment

Check 4: Git Status

  • Check for uncommitted changes
  • Check current branch
  • Verify branch is up to date with remote

Check 5: Code Quality Quick Check

  • Check for debug functions in custom code: var_dump, print_r, dpm, kint, dd, dsm
  • Check for TODO or FIXME comments in custom modules
  • Check for \Drupal::service() calls in src/ directories

Check 6: Deployment Script

Look for deployment scripts and verify they follow correct order:

  1. drush updatedb
  2. drush cache:rebuild
  3. drush config:import
  4. drush cache:rebuild
  5. drush deploy:hook (if using deploy hooks)

Report

Present a deployment readiness report:

=== DEPLOYMENT READINESS CHECK ===

Config Status:    [PASS/FAIL] - Details
Composer Lock:    [PASS/FAIL] - Details
Security Audit:   [PASS/FAIL] - Details
Database Updates: [PASS/WARN] - Details
Git Status:       [PASS/FAIL] - Details
Code Quality:     [PASS/WARN] - Details
Deploy Script:    [PASS/WARN] - Details

Overall: READY / NOT READY

If NOT READY, list what needs to be fixed before deploying.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 74 lines · 24 tokens per session scan A ad22a988659e

Subscribe to this mod's changes

deploy-check is a command published in the GitHub repository abderrahimghazali/drupal-boost (1 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 518 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code reviewDrupalGit and workflowSecurityclaude-codeclaude-code-pluginddevdrupal-moduledrupal-theme
Related

Other commands, from other repositories

module-scaffold

Generate a new Drupal module with best-practice structure.

edutrul/drupal-ai · 14 tokens

performance-check

Analyze Drupal site performance and caching configuration.

edutrul/drupal-ai · 10 tokens

code-review

Full code review of a branch, PR, or Jira ticket. Accepts a Jira ticket ID (e.g. TICKET-123), branch name, or PR number as optional input. Defaults to current branch. Runs static analysis, PHPCS, PHPStan, and Drupal best-practice checks.

edutrul/drupal-ai · 63 tokens

security-audit

Audit a Drupal site for security issues and vulnerabilities.

edutrul/drupal-ai · 13 tokens

config-export

Export Drupal configuration with proper workflow.

edutrul/drupal-ai · 9 tokens

drush-check

Run common Drush checks to verify Drupal site health.

edutrul/drupal-ai · 14 tokens