Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/edutrul/drupal-ainpx agentmods add skills/edutrul/drupal-ai/drupal-contrib-mgmtWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/edutrul/drupal-ai/drupal-contrib-mgmt)<a href="https://agentmods.dev/skills/edutrul/drupal-ai/drupal-contrib-mgmt"><img src="https://agentmods.dev/badge/skills/edutrul/drupal-ai/drupal-contrib-mgmt.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00058 | $0.01235 |
| Opus 5 | $0.00029 | $0.00617 |
| Sonnet 5 | $0.00012 | $0.00247 |
| Haiku 4.5 | $0.00006 | $0.00123 |
Grade A, and why
drupal-contrib-mgmt 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drupal Contrib Module Management
Core Update Commands
composer require drupal/module_name --with-all-dependencies
composer require drupal/module_name:^3.0 --with-all-dependencies
drush updb -y && drush cr
Checking Drupal 11 Compatibility
Fastest method — check .info.yml:
cat docroot/modules/contrib/MODULE_NAME/MODULE_NAME.info.yml | grep core_version_requirement
core_version_requirement: ^9.5 || ^10 || ^11 # D11 compatible
core_version_requirement: ^9 || ^10 # Not D11 compatible
upgrade_statuswarnings ≠ incompatible — module may still declare^11support- "Check manually" status is often a false positive (runtime version checks)
Drupal Lenient Plugin
For modules that haven't updated version requirements yet:
{
"require": { "mglaman/composer-drupal-lenient": "^1.0" },
"config": { "allow-plugins": { "mglaman/composer-drupal-lenient": true } },
"extra": {
"drupal-lenient": { "allowed-list": ["drupal/module_name"] }
}
}
Patch Management (cweagans/composer-patches)
IMPORTANT: Use 2.x — uses git apply (reliable). Version 1.x uses patch binary (fragile).
{
"require": { "cweagans/composer-patches": "^2.0" },
"config": { "allow-plugins": { "cweagans/composer-patches": true } },
"extra": {
"composer-exit-on-patch-failure": true,
"patches": {
"drupal/module_name": {
"Description of patch - Issue #3552531": "patches/module-fix-3552531-2.patch"
}
}
}
}
2.x gotcha: Hash-based caching — patches can silently go missing after reinstalls.
Verifying Patches Are Applied
./scripts/verify-patches.sh # Check all critical patches
./scripts/verify-patches.sh --fix # Auto-reinstall affected modules
Adding a new patch to verification — edit scripts/verify-patches.sh:
CRITICAL_PATCHES=(
"docroot/modules/contrib/MODULE:src/File.php:patternToFind:Description"
)
When patches go missing:
./scripts/verify-patches.shto identifycomposer reinstall drupal/module_nameor./scripts/verify-patches.sh --fix- If still failing:
composer update --lock
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/create-custom-patch.sh 4.5 KB runs code
- examples/find-and-apply-patch.sh 2.6 KB runs code
- examples/major-version-upgrade.sh 2.1 KB runs code
- examples/update-with-patch.sh 1.2 KB runs code
- README.md 5.1 KB
- references/d11-common-deprecations.md 6.7 KB
- references/drupal-patches-workflow.md 33 KB
- references/issue-queue-rss-feeds.md 7.1 KB
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.
- 8d ago First seen · 145 lines · 58 tokens per session scan A 1160d83a42f1
drupal-contrib-mgmt is a skill published in the GitHub repository edutrul/drupal-ai (71 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 1,235 once invoked, about $0.0003 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.
Other skills, from other repositories
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
fix-merge-conflicts
Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution.
cgs-bug-triage
Use for bug triage tasks that classify bugs by severity, priority, reproduction confidence, owner role, risk, and release impact; produce verification evidence, changed or proposed files, and handoff boundaries.
bisect
Use when hunting a regression, phrases like "bisect", "find the commit that broke X", "this used to work", "regression in test Y", "when did start". Also use when escalated from ci-debug-loop because log analysis can't pinpoint the offending change, or when a previously-passing test/build/behavior is now failing and…
troubleshoot-worktree
Troubleshoot git worktree, branch, and refname issues.
reconcile
Tripwire check for multi-session drift. Scans state files, recent commits, and file conflicts caused by parallel Claude Code sessions.