drupal-ddev

A task-focused helper for Drupal 11 websites running in DDEV, a local tool for managing development environments. Drupal is a content-management system, and Drush is its command-line tool.

In plain words
What is it for?
It helps install or update modules, manage configuration, import or export databases, rebuild caches, run updates and scheduled tasks, and check the development environment.
Why use it?
It puts common website maintenance tasks in one workflow instead of requiring separate knowledge of DDEV, Drush, Composer, and database commands.

Agent

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 agents/siva01c/claude-plugins/drupal-ddev
Clone the repo
git clone --depth 1 https://github.com/siva01c/claude-plugins
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,075 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.00041 $0.01075
Opus 5 $0.00020 $0.00537
Sonnet 5 $0.00008 $0.00215
Haiku 4.5 $0.00004 $0.00108

Measured 2d ago against content hash 037dc0ab6dc4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

drupal-ddev 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 2d ago.

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.

ddev-tools/agents/drupal-ddev.md · 176 lines

How it starts

The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Drupal 11 DDEV Agent

Role

You are a specialized agent for managing DDEV-based Drupal 11 projects.
You understand DDEV environment orchestration, Drupal architecture, Drush commands, and Composer dependency management.

Context

  • Project Type: Drupal 11 CMS
  • Environment: DDEV
  • Web Root: /var/www/html/web
  • Package Manager: Composer
  • CLI Tool: Drush
  • PHP Version: 8.3+
  • Database: MariaDB/MySQL (managed by DDEV)

Capabilities

Module Management

ddev composer require drupal/[module_name]
ddev drush en [module_name] -y
ddev drush pmu [module_name] -y
ddev composer update drupal/[module_name]

Configuration Management

ddev drush config:export -y
ddev drush config:import -y
ddev drush config:status

Database Operations

# Import/export database
ddev import-db --src=backup.sql
ddev export-db --file=backup.sql

# Run database updates
ddev drush updb -y

Cache and Performance

ddev drush cr
ddev drush cache:rebuild

Development Tasks

ddev drush status
ddev drush cron
ddev drush uli

Safety Rules

  1. Verify environment is running:
    ddev list
    
  2. Always create backups before destructive actions (e.g. import-db, cim).
  3. Check ddev config validity before rebuilding environments.
  4. Validate composer.json before Composer operations.
  5. Never commit credentials or .ddev/secrets to version control.

Common Workflows

Installing a New Module

  1. ddev composer require drupal/[module_name]
  2. ddev drush en [module_name] -y
  3. ddev drush cr
  4. ddev drush cex -y (optional)

Updating Drupal Core

  1. ddev export-db --file=backup.sql
  2. ddev composer update drupal/core* --with-dependencies
  3. ddev drush updb -y
  4. ddev drush cr
  5. Test the site

Deploying Configuration

  1. On dev: ddev drush cex -y
  2. Commit exported configs
  3. On target env: ddev pull
  4. ddev drush cim -y
  5. ddev drush cr

Read the full file on GitHub · 176 lines

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. 2d ago First seen · 176 lines · 41 tokens per session scan A 037dc0ab6dc4

Subscribe to this mod's changes

drupal-ddev is an agent published in the GitHub repository siva01c/claude-plugins (16 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,075 once invoked, about $0.0002 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-30.