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/module-scaffoldnpx skills add trebormc/drupal-ai-agents --skill module-scaffoldgit 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/module-scaffold)<a href="https://agentmods.dev/skills/trebormc/drupal-ai-agents/module-scaffold"><img src="https://agentmods.dev/badge/skills/trebormc/drupal-ai-agents/module-scaffold.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.01085 |
| Opus 5 | $0.00065 | $0.00543 |
| Sonnet 5 | $0.00026 | $0.00217 |
| Haiku 4.5 | $0.00013 | $0.00109 |
Grade A, and why
module-scaffold 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 4d 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.
Environment
All commands run via ssh web. All modules go in
$DDEV_DOCROOT/modules/custom/. Never hardcode web/ — use $DDEV_DOCROOT
(detect with grep "^docroot:" .ddev/config.yaml).
Module structure
Replace every {module_name} placeholder with the module machine name (lowercase, underscores, e.g. event_manager) and {Module Name} with the human-readable name.
$DDEV_DOCROOT/modules/custom/{module_name}/
├── {module_name}.info.yml
├── {module_name}.module
├── {module_name}.services.yml
├── {module_name}.routing.yml
├── {module_name}.permissions.yml
├── {module_name}.links.menu.yml # If admin UI needed
├── config/
│ ├── install/ # Default config
│ └── schema/
│ └── {module_name}.schema.yml # REQUIRED for all config
├── src/
│ ├── Controller/ # Route controllers
│ ├── Form/ # Config and custom forms
│ ├── Service/ # Business logic services
│ └── Plugin/ # Block, Field, etc.
└── tests/
└── src/
├── Unit/ # Pure logic tests
├── Kernel/ # Service integration tests
└── Functional/ # Full browser tests
info.yml template
name: '{Module Name}'
type: module
description: '{Brief description}'
package: Custom
core_version_requirement: ^10.3 || ^11
php: 8.3
dependencies: []
services.yml template
services:
{module_name}.{service_name}:
class: Drupal\{module_name}\Service\{ServiceName}
arguments:
- '@entity_type.manager'
- '@logger.factory'
- '@cache.default'
Controller template
<?php
declare(strict_types=1);
namespace Drupal\{module_name}\Controller;
use Drupal\Core\Controller\ControllerBase;
use Symfony\Component\DependencyInjection\ContainerInterface;
final class {ControllerName} extends ControllerBase {
public static function create(ContainerInterface $container): static {
return new static(
// Inject services here
);
}
public function __construct(
// Type-hinted constructor parameters
) {}
}
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.
- 4d ago First seen · 145 lines · 130 tokens per session scan A ea33c1ce0bb0
module-scaffold 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,085 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…