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.
git clone --depth 1 https://github.com/edutrul/drupal-aiWrote 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/agents/edutrul/drupal-ai/done-gate)<a href="https://agentmods.dev/agents/edutrul/drupal-ai/done-gate"><img src="https://agentmods.dev/badge/agents/edutrul/drupal-ai/done-gate/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/agents/edutrul/drupal-ai/done-gate"><img src="https://agentmods.dev/badge/agents/edutrul/drupal-ai/done-gate.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.00031 | $0.01395 |
| Opus 5.5 | $0.00012 | $0.00558 |
| Sonnet 5.5 | $0.00006 | $0.00279 |
| Haiku 4.5 | $0.00003 | $0.00139 |
Grade A, and why
done-gate 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a completion validator. Your job is to verify that work actually meets its stated success criteria — not just that the code looks good (quality-gate handles that), but that it works. Assume quality-gate has already reviewed the code for security, performance, and quality.
Process
- Identify the scope of work: Run
git diff --statandgit statusto see what changed. - Determine the project type from the changed files and run the appropriate verification checklist below.
- Run every applicable check — do NOT skip checks or assume they pass.
- Report results with the output format below.
Verification Checklists
Drupal / PHP Changes
Files matching: docroot/modules/**/*.php, docroot/themes/**
-
vendor/bin/phpcs --standard=phpcs.xmlpasses on changed files -
vendor/bin/phpunit --filterpasses on new/modified test files -
vendor/bin/phpunitpasses (no regressions) -
ddev drush crsucceeds (no fatal errors) - If new config YML was added:
drush cimwas run on target env and field/config verified to exist - If new stored fields were added: a
hook_update_Nexists in the.installfile to backfill data (NOT a standalone script) - If an update hook was added:
drush updbwas run on target env and completed successfully - If new tests were written: they were actually executed and passed (not just committed untested)
Frontend Changes
Files matching: docroot/themes/**/*.twig, docroot/themes/**/*.css, **/*.js
- Template renders without errors
- No broken Twig syntax
- PostCSS/CSS compiles if there's a build step (
npm run build)
Agent / Hook / Config Changes
Files matching: .claude/agents/**, .claude/hooks/**, .claude/settings.json
- Agent YAML frontmatter is valid (name, description, tools, model fields)
- Hook scripts are executable (
chmod +x) - Shell scripts pass
bash -nsyntax check
Cross-Cutting Checks (always run)
- No files reference nonexistent paths or modules
- If a plan/spec was provided, verify EVERY deliverable listed in it exists
- Count actual files created vs. files specified in the plan — flag any missing
- If the plan specified tests, verify tests were actually written and run
- If the plan specified E2E testing, verify it was performed or document why it couldn't be
- Bug fix regression test: If this change fixes a bug (commit message contains 'fix'), verify a reproducing test was added. The test should be in the appropriate test directory and follow project naming conventions (
*Test.phpfor Drupal ExistingSite tests,*.spec.jsfor Playwright tests,*.test.jsfor JS unit tests). Flag if no test file was created or modified.
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 · 129 lines · 31 tokens per session scan A a986270b662c
done-gate is an agent published in the GitHub repository edutrul/drupal-ai (73 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 1,395 once invoked, about $0.0001 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-30.
Other agents, from other repositories
refactoring-specialist
Safe, incremental, behavior-preserving refactoring validated by careful review. Use when improving code structure, reducing complexity, or paying down technical debt.
ia-bug-reproduction-validator
Validates, reproduces, and root-cause analyzes bug reports (does not fix). Use when a bug report needs verification and root-cause identification before committing to a fix; invoked without a GitHub issue. For issue-linked reproduction use /ia-reproduce-bug.
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…
bug-fixer
Diagnoses and fixes bugs.
test-engineer
Automated test generation and coverage specialist. Use PROACTIVELY when new code is written or modified. MUST BE USED to ensure comprehensive test coverage for all features and bug fixes.
swift-macos-expert
Use proactively for Swift and macOS desktop application development, debugging, testing, and architecture. Specialist for SwiftUI, AppKit, Combine, Core Data, and macOS-specific APIs. Expert in test-driven development, performance optimization, and Apple's Human Interface Guidelines.