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 agentmods add skills/trebormc/drupal-ai-agents/drupal-migrationnpx skills add trebormc/drupal-ai-agents --skill drupal-migrationgit 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/drupal-migration)<a href="https://agentmods.dev/skills/trebormc/drupal-ai-agents/drupal-migration"><img src="https://agentmods.dev/badge/skills/trebormc/drupal-ai-agents/drupal-migration.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 | $0.00130 | $0.01263 |
| Opus 5 | $0.00065 | $0.00632 |
| Sonnet 5 | $0.00026 | $0.00253 |
| Haiku 4.5 | $0.00013 | $0.00126 |
Grade A, and why
drupal-migration 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 3d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Environment
All commands via ssh web drush.
Required modules
ssh web composer require drupal/migrate_plus drupal/migrate_tools drupal/migrate_upgrade
ssh web drush en migrate migrate_plus migrate_tools -y
Migration YAML structure
Place in config/install/ or migrations/ directory:
id: my_migration
label: 'Migrate content from source'
migration_group: my_group
source:
plugin: csv
path: private://import/data.csv
ids: [id]
header_offset: 0
process:
type:
plugin: default_value
default_value: article
title: title
body/value: body
body/format:
plugin: default_value
default_value: basic_html
field_date:
plugin: format_date
source: date
from_format: 'm/d/Y'
to_format: 'Y-m-d'
destination:
plugin: 'entity:node'
migration_dependencies:
required: []
optional: []
Common migration commands
| Task | Command |
|---|---|
| List migrations | ssh web drush migrate:status |
| Run migration | ssh web drush migrate:import my_migration |
| Run with limit | ssh web drush migrate:import my_migration --limit=10 |
| Rollback (undo imported rows) | ssh web drush migrate:rollback my_migration |
| Reset stuck "Importing" status | ssh web drush migrate:reset-status my_migration |
| Run all in group | ssh web drush migrate:import --group=my_group |
| Update existing | ssh web drush migrate:import my_migration --update |
D7 to D10/D11 workflow
Step 1: Generate migration config
ssh web drush migrate:upgrade --legacy-db-key=d7 --configure-only
Step 2: Review and customize
ssh web drush cex -y
# Review migrate_plus.migration.* files in config/sync/
Step 3: Test with limits
ssh web drush migrate:import upgrade_d7_node_article --limit=5
Step 4: Verify and run full
ssh web drush migrate:import --all
Custom source plugin template
<?php
declare(strict_types=1);
namespace Drupal\mymodule\Plugin\migrate\source;
use Drupal\migrate\Plugin\migrate\source\SqlBase;
use Drupal\migrate\Row;
/**
* @MigrateSource(id = "my_custom_source")
*/
final class MyCustomSource extends SqlBase {
public function query(): \Drupal\Core\Database\Query\SelectInterface {
return $this->select('source_table', 's')
->fields('s', ['id', 'title', 'body', 'created']);
}
public function fields(): array {
return [
'id' => $this->t('Unique ID'),
'title' => $this->t('Title'),
];
}
public function getIds(): array {
return ['id' => ['type' => 'integer']];
}
public function prepareRow(Row $row): bool {
return parent::prepareRow($row);
}
}
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.
- 3d ago First seen · 175 lines · 130 tokens per session scan A e9cd7b2ef82c
drupal-migration is a skill published in the GitHub repository trebormc/drupal-ai-agents (10 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 130 tokens to every session and 1,263 once invoked, about $0.0006 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…