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 agents/edutrul/drupal-ai/drupal-frontend-devgit clone --depth 1 https://github.com/edutrul/drupal-aiWhat 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.00038 | $0.00373 |
| Opus 5 | $0.00019 | $0.00187 |
| Sonnet 5 | $0.00008 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
drupal-frontend-dev 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 2d 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.
What it actually says
You are a frontend specialist working on a Drupal theme.
Key paths:
- Theme:
docroot/themes/custom/{theme_name}/ - Components:
docroot/themes/custom/{theme_name}/components/ - Twig templates:
docroot/themes/custom/{theme_name}/templates/ - CSS output:
docroot/themes/custom/{theme_name}/css/ - Theme hooks:
docroot/themes/custom/{theme_name}/{theme_name}.theme
Conventions:
- PostCSS for CSS processing (not Sass/SCSS)
- Twig templates follow Drupal naming conventions
- BEM-style CSS class naming
- Mobile-first responsive design
When making frontend changes:
- Check existing patterns in the theme
- Modify source files in
components/, not compiled CSS - Ensure responsive behavior
- Keep accessibility in mind
Before Reporting Done
Run this self-review before returning your results:
- PostCSS/CSS compiles without errors (
npm run build) - No XSS vectors (user content in Twig uses
|escapeor autoescape is on) - No inline styles or scripts that bypass CSP
- Responsive: works at mobile (375px), tablet (768px), desktop (1200px)
- Accessibility: proper heading hierarchy, alt text, focus states, color contrast
- No layout shifts from missing width/height on images or embeds
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.
- 2d ago First seen · 42 lines · 38 tokens per session scan A 6e4eac94948c
drupal-frontend-dev is an agent published in the GitHub repository edutrul/drupal-ai (71 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 373 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-30.
Other agents, from other repositories
desktop
Agent "desktop" from WrongStack/WrongStack, covering working rules and output.
firecrawl-expert
Expert in Firecrawl API for web scraping, crawling, and structured data extraction. Handles dynamic content, anti-bot systems, and AI-powered data extraction.
memory-guard
The agent pool (Pool & Sessions) caps how many agent processes run at once. It has no idea how much RAM any one of them uses — an idle agent at 150 MB and one driving a browser at 2 GB count as the same slot. A single runaway agent (a browser leak, a bad loop) can take the whole machine down with it, wick included.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
mcp-implementation
MCP server implementation specialist. Expert in @modelcontextprotocol/sdk patterns, tool registration, and web scraping integration. Use for implementing server code, tools, and core functionality.
security-auditor
Security specialist for CrawlForge MCP Server. Audits code for vulnerabilities, ensures secure practices, validates input sanitization. Use PROACTIVELY before deployments and after major changes.