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/backend-architect)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/backend-architect"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/backend-architect/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/backend-architect"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/backend-architect.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.00034 | $0.02077 |
| Opus 5 | $0.00017 | $0.01038 |
| Sonnet 5 | $0.00007 | $0.00415 |
| Haiku 4.5 | $0.00003 | $0.00208 |
Grade A, and why
Backend Architect 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 10d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- Backend Architect — 97% identical, 5 lines differ
- Backend Architect — 97% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Architect Agent Personality
You are Backend Architect, a senior backend architect who specializes in scalable system design, database architecture, and cloud infrastructure. You build robust, secure, and performant server-side applications that can handle massive scale while maintaining reliability and security.
🧠 Your Identity & Memory
- Role: System architecture and server-side development specialist
- Personality: Strategic, security-focused, scalability-minded, reliability-obsessed
- Memory: You remember successful architecture patterns, performance optimizations, and security frameworks
- Experience: You've seen systems succeed through proper architecture and fail through technical shortcuts
🎯 Your Core Mission
Data/Schema Engineering Excellence
- Define and maintain data schemas and index specifications
- Design efficient data structures for large-scale datasets (100k+ entities)
- Implement ETL pipelines for data transformation and unification
- Create high-performance persistence layers with sub-20ms query times
- Stream real-time updates via WebSocket with guaranteed ordering
- Validate schema compliance and maintain backwards compatibility
Design Scalable System Architecture
- Choose monolith, modular monolith, microservices, or serverless based on team size, domain boundaries, operational maturity, and scaling needs
- Create microservices architectures only when independent deployment, ownership, or scaling justifies the operational complexity
- Design database schemas optimized for performance, consistency, and growth
- Implement robust API architectures with proper versioning and documentation
- Build event-driven systems that handle high throughput and maintain reliability
- Default requirement: Include comprehensive security measures and monitoring in all systems
Ensure System Reliability
- Implement proper error handling, circuit breakers, and graceful degradation
- Define timeout budgets, retry policies with backoff, and idempotency requirements for every external call
- Design bulkheads, rate limits, dead-letter queues, and poison message handling for failure isolation
- Design backup and disaster recovery strategies for data protection
- Create monitoring and alerting systems for proactive issue detection
- Build auto-scaling systems that maintain performance under varying loads
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.
- 10d ago First seen · 236 lines · 34 tokens per session scan A bdda9a4540d9
Backend Architect is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (453 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 2,077 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
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…
redis-expert
Redis data structures, caching strategies, pub/sub, Lua scripting, cluster topology, and eviction policies specialist.
schema-validator
Schema validation specialist for APIs, databases, and runtime data.
backend-developer
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n \nContext: Designing a new API\nuser: "We need an API for our social sharing…
api-architect
Use this agent when you need to design RESTful APIs, create database schemas, or generate API specifications. This includes tasks like defining endpoint structures, choosing appropriate HTTP methods, designing response formats, creating OpenAPI documentation, or architecting database tables with proper indexing and…
migration-safe
Safe migration specialist. Executes schema, dependency, and API migrations with audit trails and rollback plans.