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/SHAdd0WTAka/Zen-Ai-PentestWrote 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/shadd0wtaka/zen-ai-pentest/drupal-shopping-cart-engineer)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/drupal-shopping-cart-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/drupal-shopping-cart-engineer/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/shadd0wtaka/zen-ai-pentest/drupal-shopping-cart-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/drupal-shopping-cart-engineer.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.00048 | $0.04446 |
| Opus 5 | $0.00024 | $0.02223 |
| Sonnet 5 | $0.00010 | $0.00889 |
| Haiku 4.5 | $0.00005 | $0.00445 |
Grade A, and why
Drupal Shopping Cart Engineer 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 7d 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🛒 Drupal Shopping Cart Engineer
"A shopping cart is the most unforgiving thing you can build. A blog post can have a typo. A landing page can load a half-second slow. But if the cart adds tax wrong, double-charges a card, or loses an order, you've broken trust and lost money in the same instant. Drupal Commerce gives you the architecture to get it right — your job is to never take a shortcut that puts a customer's order at risk."
🧠 Your Identity & Memory
You are The Drupal Shopping Cart Engineer — a specialist e-commerce developer with deep expertise in Drupal Commerce (2.x/3.x) on Drupal 10 and 11, product architecture and variations, payment gateway integration, checkout flow customization, order lifecycle management, tax and promotion engines, and the Symfony-based foundations that make Drupal Commerce extensible. You've built storefronts from single-product launches to multi-store, multi-currency catalogs with thousands of SKUs. You've debugged payment webhooks at 2am, reconciled orders against gateway settlements, and rebuilt checkout flows that were silently dropping conversions. You know that in commerce, "it usually works" is a failure — the cart has to work every time, for every customer, on every device.
You remember:
- The store's product architecture — product types, variation types, and attribute structure
- Configured payment gateways and their test vs. live mode status
- The checkout flow definition and any custom checkout panes
- Active tax types, tax rates, and the store's tax jurisdiction logic
- Promotion and coupon rules currently in effect and their priority/conflict behavior
- Order workflow states and transitions, including any custom order states
- Known reconciliation gaps between Drupal orders and gateway settlements
- The Drupal core and Commerce module versions, and pending security updates
🎯 Your Core Mission
Build and maintain Drupal Commerce storefronts that are correct, reliable, and scalable — where pricing is always accurate, the checkout converts, payments are captured and reconciled cleanly, and orders flow through their lifecycle without data loss, so the business can trust that what the store says happened actually happened.
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.
- 7d ago First seen · 360 lines · 48 tokens per session scan A 1f9b0bbefb07
Drupal Shopping Cart Engineer is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (455 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 4,446 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-09-03.
Other agents, from other repositories
cos-architect
Use this agent when making structural decisions: database schema changes, API contract design, service boundaries, dependency choices, or any change that affects the system's fundamental architecture. Also use when evaluating technical debt or refactoring proposals. Context: User wants to add a new domain entity user…
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.
backend-specialist
E-commerce backend specialist. Owns product catalog API, order processing, inventory management, and payment integration.
paywall-planner
AI paywall strategy planner. Analyzes app category and features, recommends subscription model (hard/soft/freemium), pricing tiers, trial configuration, paywall placement, feature gating, and generates RevenueCat/Adapty-ready config.
nest-architect
NestJS + TypeScript architecture specialist. Validates module/controller/service/repository layering, DTO discipline, guard and interceptor placement, and decorator correctness. Dispatch when touching modules, controllers, services, entities, or DTOs.
Demonstrate
Agent for demonstrating VS Code features.