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.
npx skills add trebormc/drupal-ai-agents --skill drush-commandsgit clone --depth 1 https://github.com/trebormc/drupal-ai-agentsWrote 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/trebormc/drupal-ai-agents/drush-commands)<a href="https://agentmods.dev/skills/trebormc/drupal-ai-agents/drush-commands"><img src="https://agentmods.dev/badge/skills/trebormc/drupal-ai-agents/drush-commands.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.00131 | $0.00792 |
| Opus 5 | $0.00066 | $0.00396 |
| Sonnet 5 | $0.00026 | $0.00158 |
| Haiku 4.5 | $0.00013 | $0.00079 |
Grade A, and why
drush-commands 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Environment
All Drush commands run via ssh web drush.
NEVER use just drush — it will not be found without the full vendor path.
Common operations
| Task | Command |
|---|---|
| Clear all caches | ssh web drush cr |
| Run database updates | ssh web drush updb -y |
| Enable module | ssh web drush en <module> -y |
| Uninstall module | ssh web drush pmu <module> -y |
| Check Drupal status | ssh web drush status |
| Run cron | ssh web drush cron |
| One-time login | ssh web drush uli |
| List enabled modules | ssh web drush pm:list --status=enabled |
| Check pending updates | ssh web drush updb --no |
| Watchdog logs | ssh web drush ws --count=20 |
| Rebuild permissions | ssh web drush php-eval "node_access_rebuild();" |
| Locale update | ssh web drush locale:check && ssh web drush locale:update |
After code changes (mandatory order)
ssh web drush updb -y(apply hook_update_N)ssh web drush cim -y(import config changes)ssh web drush cr(rebuild caches)
Multiline / newline-separated config values
drush cget <config> <key> --format=string renders real newlines as literal \n
text. Feeding that back through drush cset stores the literal backslash-n and
corrupts every existing line. To append to or edit a multiline value, use
php:eval, then verify with var_export:
# Append a line to a newline-separated value:
ssh web drush php:eval '$c=\Drupal::configFactory()->getEditable("mymodule.settings"); $c->set("patterns", $c->get("patterns")."\nnew-pattern")->save();'
# Verify the stored value has REAL newlines, not literal \n:
ssh web drush php:eval 'var_export(\Drupal::config("mymodule.settings")->get("patterns"));'
Custom Drush commands (Drush 12+)
Place in src/Commands/ using attribute pattern:
<?php
declare(strict_types=1);
namespace Drupal\mymodule\Commands;
use Drush\Attributes as CLI;
use Drush\Commands\DrushCommands;
final class MyModuleCommands extends DrushCommands {
#[CLI\Command(name: 'mymodule:process')]
#[CLI\Help(description: 'Process pending items.')]
public function process(): void {
$this->io()->success('Done.');
}
}
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 · 89 lines · 131 tokens per session scan A 2817d144b84d
drush-commands is a skill published in the GitHub repository trebormc/drupal-ai-agents (10 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 131 tokens to every session and 792 once invoked, about $0.0007 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…