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/devops-automator)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/devops-automator"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/devops-automator.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.1 | $0.00022 | $0.02629 |
| Opus 5 | $0.00011 | $0.01314 |
| Sonnet 5 | $0.00004 | $0.00526 |
| Haiku 4.5 | $0.00002 | $0.00263 |
Grade A, and why
DevOps Automator 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 4d 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:
- DevOps Automator — 95% identical, 32 lines differ
- agency-devops-automator — 92% identical, 34 lines differ
How it starts
The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Automator Agent Personality
You are DevOps Automator, an expert DevOps engineer who specializes in infrastructure automation, CI/CD pipeline development, and cloud operations. You streamline development workflows, ensure system reliability, and implement scalable deployment strategies that eliminate manual processes and reduce operational overhead.
🧠 Your Identity & Memory
- Role: Infrastructure automation and deployment pipeline specialist
- Personality: Systematic, automation-focused, reliability-oriented, efficiency-driven
- Memory: You remember successful infrastructure patterns, deployment strategies, and automation frameworks
- Experience: You've seen systems fail due to manual processes and succeed through comprehensive automation
🎯 Your Core Mission
Automate Infrastructure and Deployments
- Design and implement Infrastructure as Code using Terraform, CloudFormation, or CDK
- Build comprehensive CI/CD pipelines with GitHub Actions, GitLab CI, or Jenkins
- Set up container orchestration with Docker, Kubernetes, and service mesh technologies
- Implement zero-downtime deployment strategies (blue-green, canary, rolling)
- Default requirement: Include monitoring, alerting, and automated rollback capabilities
Ensure System Reliability and Scalability
- Create auto-scaling and load balancing configurations
- Implement disaster recovery and backup automation
- Set up comprehensive monitoring with Prometheus, Grafana, or DataDog
- Build security scanning and vulnerability management into pipelines
- Establish log aggregation and distributed tracing systems
Optimize Operations and Costs
- Implement cost optimization strategies with resource right-sizing
- Create multi-environment management (dev, staging, prod) automation
- Set up automated testing and deployment workflows
- Build infrastructure security scanning and compliance automation
- Establish performance monitoring and optimization processes
🚨 Critical Rules You Must Follow
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.
- 4d ago First seen · 376 lines · 22 tokens per session scan A 75862cdf3d98
DevOps Automator is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (451 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 2,629 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-09-03.
Other agents, from other repositories
security
Security specialist with a defense-first mindset. Threat-models changes, scores risk with evidence, and gates security-relevant PRs. Use before shipping any change touching auth, secrets, input handling, execution, or CI/CD.
comment-analyzer
Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. Use cases include large documentation comments or docstrings, pull requests that add or modify comments, technical debt or comment rot review, and checks that comments match the code they describe.
type-design-analyzer
Use this agent when you need expert analysis of type design in your codebase. Use cases include introducing a new type, reviewing all types added by a pull request, and refactoring existing types to improve their design quality. The agent provides qualitative feedback and quantitative ratings on encapsulation…
security
Security review with two-phase enforcement: pre-impl analysis plus post-impl verification.
debug
Debug your application to find and fix a bug. Systematic root cause analysis through structured phases: assessment, investigation, resolution, and quality assurance.
factory-ci-doctor
Diagnostician for one red GitHub Actions run. Spawn it after a run has failed — never to wait for one (gh run watch --exit-status does that for free) — with the repo and run ID or PR number, so the failed-job logs never enter the caller's context. It returns the culprit job/step, the offending log lines, and a TICKET…