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 drupal-org-contribution-prepgit 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-org-contribution-prep)<a href="https://agentmods.dev/skills/trebormc/drupal-ai-agents/drupal-org-contribution-prep"><img src="https://agentmods.dev/badge/skills/trebormc/drupal-ai-agents/drupal-org-contribution-prep/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/trebormc/drupal-ai-agents/drupal-org-contribution-prep"><img src="https://agentmods.dev/badge/skills/trebormc/drupal-ai-agents/drupal-org-contribution-prep.svg" alt="Reviewed on agentmods" width="80" 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.00179 | $0.01300 |
| Opus 5.5 | $0.00072 | $0.00520 |
| Sonnet 5.5 | $0.00036 | $0.00260 |
| Haiku 4.5 | $0.00018 | $0.00130 |
Grade A, and why
drupal-org-contribution-prep 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 1mo 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drupal.org Contribution Prep
A module can be functionally perfect and still present badly. Fix presentation before
contributing. All test commands via ssh web.
1. Test-suite registration (the silent-failure trap)
phpunit.xml.dist MUST declare unit, kernel AND functional suites. A project declaring
only unit accumulates kernel failures nobody sees (in the field: 10 kernel failures + a
missing fixtures directory went unnoticed for months).
<testsuites>
<testsuite name="unit">
<directory>web/modules/custom/*/tests/src/Unit</directory>
</testsuite>
<testsuite name="kernel">
<directory>web/modules/custom/*/tests/src/Kernel</directory>
</testsuite>
<testsuite name="functional">
<directory>web/modules/custom/*/tests/src/Functional</directory>
</testsuite>
</testsuites>
(Adapt web/ to the real $DDEV_DOCROOT.) Then actually RUN all three suites — do not stop at
registering them. Also verify every fixture path referenced in any setUp() exists in the repo:
grep -rn "fixtures" $DDEV_DOCROOT/modules/custom/<module>/tests --include=*.php | grep -oE "[A-Za-z0-9_./-]*fixtures[A-Za-z0-9_./-]*" | sort -u
# ls each resulting path — a missing directory means tests silently test nothing.
2. GitLab CI
.gitlab-ci.yml including the official gitlab_templates ($_GITLAB_TEMPLATES_REPO) with
opt-ins matching the declared core range:
include:
- project: $_GITLAB_TEMPLATES_REPO
ref: $_GITLAB_TEMPLATES_REF
file: .gitlab-ci.yml
variables:
OPT_IN_TEST_PREVIOUS_MAJOR: 1
OPT_IN_TEST_NEXT_MINOR: 1
OPT_IN_TEST_NEXT_MAJOR: 1
A green pipeline is the first thing reviewers look at. Layout gotcha: the module's own
phpstan.neon on drupal.org CI resolves includes against an ADJACENT vendor/; installed under
modules/contrib those includes fail. Document a local-equivalent config rather than "fixing"
the neon — it is correct for its target environment.
3. Repository hygiene
- Remove orphaned dirs (empty submodule stubs, stale fixture duplicates). Upgrade Status parses ALL Twig files, so a broken leftover fixture becomes a public finding in bot issues.
- Check the git INDEX, not just the worktree — staged-then-deleted ghost files ride along silently:
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.
- 1mo ago First seen · 126 lines · 179 tokens per session scan A e616a1a03c39
drupal-org-contribution-prep is a skill published in the GitHub repository trebormc/drupal-ai-agents (11 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 179 tokens to every session and 1,300 once invoked, about $0.0007 per session on Opus 5.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
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.