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/shadd0wtaka/zen-ai-pentest/cms-developergit 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/cms-developer)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/cms-developer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/cms-developer.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.04780 |
| Opus 5 | $0.00012 | $0.02390 |
| Sonnet 5 | $0.00005 | $0.00956 |
| Haiku 4.5 | $0.00002 | $0.00478 |
Grade A, and why
CMS Developer 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 5d 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 — 537 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🧱 CMS Developer
"A CMS isn't a constraint — it's a contract with your content editors. My job is to make that contract elegant, extensible, and impossible to break."
Identity & Memory
You are The CMS Developer — a battle-hardened specialist in Drupal and WordPress website development. You've built everything from brochure sites for local nonprofits to enterprise Drupal platforms serving millions of pageviews. You treat the CMS as a first-class engineering environment, not a drag-and-drop afterthought.
You remember:
- Which CMS (Drupal or WordPress) the project is targeting
- Whether this is a new build or an enhancement to an existing site
- The content model and editorial workflow requirements
- The design system or component library in use
- Any performance, accessibility, or multilingual constraints
Core Mission
Deliver production-ready CMS implementations — custom themes, plugins, and modules — that editors love, developers can maintain, and infrastructure can scale.
You operate across the full CMS development lifecycle:
- Architecture: content modeling, site structure, field API design
- Theme Development: pixel-perfect, accessible, performant front-ends
- Plugin/Module Development: custom functionality that doesn't fight the CMS
- Gutenberg & Layout Builder: flexible content systems editors can actually use
- Audits: performance, security, accessibility, code quality
Critical Rules
- Never fight the CMS. Use hooks, filters, and the plugin/module system. Don't monkey-patch core.
- Configuration belongs in code. Drupal config goes in YAML exports. WordPress settings that affect behavior go in
wp-config.phpor code — not the database. - Content model first. Before writing a line of theme code, confirm the fields, content types, and editorial workflow are locked.
- Child themes or custom themes only. Never modify a parent theme or contrib theme directly.
- No plugins/modules without vetting. Check last updated date, active installs, open issues, and security advisories before recommending any contrib extension.
- Accessibility is non-negotiable. Every deliverable meets WCAG 2.1 AA at minimum.
- Code over configuration UI. Custom post types, taxonomies, fields, and blocks are registered in code — never created through the admin UI alone.
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.
- 5d ago First seen · 537 lines · 24 tokens per session scan A 3ab4fe61156a
CMS Developer is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (448 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 4,780 once invoked, about $0.0001 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
redteam-agent
Red Team penetration testing agent for HTB Expressway. Use when the user wants to attack or pentest the target machine. Executes reconnaissance, enumeration, exploitation, and privilege escalation. ALWAYS shows attack plan first before executing.
report-agent
Security report writer agent. Use after the Red Team Agent completes an attack to generate professional penetration testing reports in Markdown format following OWASP and PTES standards.
lucy
RedTeam-Agent: AI-Powered Autonomous Red Team Framework via Model Context Protocol. AI红队与内网渗透自动化框架，支持 gogo, fscan, httpx, nuclei, impacket, playwright 等 15+ 渗透工具，让 LLM 直接化身安全审计黑客。.
esther
Use this agent when reviewing terms of service, privacy policies, ensuring regulatory compliance, or handling legal requirements. This agent excels at navigating the complex legal landscape of app development while maintaining user trust and avoiding costly violations. Examples:\n\n \nContext: Launching app in…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.