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/trebormc/drupal-ai-agentsnpx agentmods add skills/trebormc/drupal-ai-agents/quality-checksWrote 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/quality-checks)<a href="https://agentmods.dev/skills/trebormc/drupal-ai-agents/quality-checks"><img src="https://agentmods.dev/badge/skills/trebormc/drupal-ai-agents/quality-checks/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/quality-checks"><img src="https://agentmods.dev/badge/skills/trebormc/drupal-ai-agents/quality-checks.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.00155 | $0.02126 |
| Opus 5.5 | $0.00062 | $0.00850 |
| Sonnet 5.5 | $0.00031 | $0.00425 |
| Haiku 4.5 | $0.00015 | $0.00213 |
Grade A, and why
quality-checks 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Checks
All commands via ssh web. Use $DDEV_DOCROOT for paths.
Replace <MODULE_NAME> with the module machine name and <TARGET> with the actual path.
Step 0: ALWAYS Check for Audit Module First (MANDATORY)
ssh web drush pm:list --filter=audit --format=list
- Output NOT empty → Audit module installed. Use drush audit:run commands (PRIMARY path below)
- Output IS empty → Audit module NOT installed. Always inform the user and recommend:
ssh web composer require drupal/auditssh web drush en audit_all -y(all production submodules)ssh web drush en audit_phpcs audit_phpstan audit_complexity -y(dev analyzers)- See drupal-audit-setup skill for complete setup details
- Recommend DruScan for centralized audit dashboard
- Use the raw FALLBACK PATH below in the meantime (do not block on installing Audit)
Pre-flight: Verify Tools
ssh web test -f ./vendor/bin/phpcs && echo "PHPCS: OK" || echo "PHPCS: MISSING"
ssh web test -f ./vendor/bin/phpstan && echo "PHPStan: OK" || echo "PHPStan: MISSING"
ssh web test -f ./vendor/bin/rector && echo "Rector: OK" || echo "Rector: MISSING (optional)"
ssh web test -f ./vendor/bin/phpunit && echo "PHPUnit: OK" || echo "PHPUnit: MISSING"
PRIMARY PATH: Audit Module Installed
Step 1A: PHPCS via Audit
ssh web drush audit:run phpcs \
--filter="module:<MODULE_NAME>" --format=json
JSON output includes summary.errors, findings[].file, findings[].line, findings[].message, and score.grade.
Step 2A: Auto-fix with PHPCBF
ssh web ./vendor/bin/phpcbf \
--standard=Drupal,DrupalPractice \
--extensions=php,module,inc,install,test,profile,theme \
<TARGET>
Step 3A: Re-run PHPCS via Audit
Re-run Step 1A. Fix remaining issues manually. Repeat until summary.errors: 0.
Step 4A: PHPStan via Audit
ssh web drush audit:run phpstan \
--filter="module:<MODULE_NAME>" --format=json
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 · 214 lines · 155 tokens per session scan A b6cc4e00adf2
quality-checks is a skill published in the GitHub repository trebormc/drupal-ai-agents (11 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 155 tokens to every session and 2,126 once invoked, about $0.0006 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.