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/abderrahimghazali/drupal-boostnpx agentmods add skills/abderrahimghazali/drupal-boost/config-managementWrote 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/abderrahimghazali/drupal-boost/config-management)<a href="https://agentmods.dev/skills/abderrahimghazali/drupal-boost/config-management"><img src="https://agentmods.dev/badge/skills/abderrahimghazali/drupal-boost/config-management.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.00040 | $0.00739 |
| Opus 5 | $0.00020 | $0.00369 |
| Sonnet 5 | $0.00008 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
config-management 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 6d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drupal Configuration Management
Core Concepts
Configuration is stored in YAML files and tracked in the config/sync directory (set in settings.php via $settings['config_sync_directory']).
Essential Commands
# Export all config
drush config:export # or drush cex
# Import all config
drush config:import # or drush cim
# Check status (what's changed)
drush config:status # or drush cst
# Export single config
drush config:get system.site
# Set single value
drush config:set system.site name "My Site"
Config Split (Multi-Environment)
Install: composer require drupal/config_split
Setup for dev/staging/prod
# config/sync/config_split.config_split.dev.yml
id: dev
label: Development
folder: ../config/splits/dev
status: true
weight: 0
module:
devel: 0
kint: 0
webprofiler: 0
theme: {}
complete_list: []
partial_list: []
Activate per environment in settings.php
// settings.php
$config['config_split.config_split.dev']['status'] = FALSE;
$config['config_split.config_split.prod']['status'] = FALSE;
// settings.local.php (dev only)
$config['config_split.config_split.dev']['status'] = TRUE;
// settings.prod.php (prod only)
$config['config_split.config_split.prod']['status'] = TRUE;
Config Split Commands
drush config-split:export dev # or drush csex dev
drush config-split:import dev # or drush csim dev
Config Overrides in settings.php
Override any config at runtime (not exported):
// Disable caching in development
$config['system.performance']['css']['preprocess'] = FALSE;
$config['system.performance']['js']['preprocess'] = FALSE;
// Change site name per environment
$config['system.site']['name'] = 'My Site (Dev)';
Config Schema
Always define schema for custom config in config/schema/MODULE_NAME.schema.yml:
MODULE_NAME.settings:
type: config_object
label: 'Module settings'
mapping:
api_key:
type: string
label: 'API Key'
max_items:
type: integer
label: 'Maximum items'
enabled:
type: boolean
label: 'Enabled'
What ships with it
2 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.
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.
- 6d ago First seen · 121 lines · 40 tokens per session scan A 9d3e746213d8
config-management is a skill published in the GitHub repository abderrahimghazali/drupal-boost (1 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 739 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-31.
Other skills, from other repositories
octopus-architecture
System architecture and API design with multi-AI consensus — use for design reviews and new subsystems.
add-cloud-flow
Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flows to additional…
list-connections
Lists Power Platform connections in the current environment. Use when you need a connection ID before adding a connector to a code app.
better-auth
Skill for integrating Better Auth - comprehensive TypeScript authentication framework for Cloudflare D1, Next.js, Nuxt, and 15+ frameworks. Use when adding auth, encountering D1 adapter errors, or implementing OAuth/2FA/RBAC features.
cloudflare-email-routing
Cloudflare Email Routing for receiving/sending emails via Workers. Use for email workers, forwarding, allowlists, or encountering Email Trigger errors, worker call failures, SPF issues.
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.