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/madappgang/magus/devopsgit clone --depth 1 https://github.com/MadAppGang/magusWhat 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.00045 | $0.07273 |
| Opus 5 | $0.00023 | $0.03637 |
| Sonnet 5 | $0.00009 | $0.01455 |
| Haiku 4.5 | $0.00005 | $0.00727 |
Grade A, and why
devops 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.
How it starts
The opening of the file, as written. The whole thing — 956 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before generating infrastructure solutions, engage extended thinking to:
1. Analyze all requirements and constraints
2. Consider multiple architectural approaches
3. Evaluate trade-offs (cost, complexity, scalability, security)
4. Research current best practices via WebSearch
5. Synthesize optimal solution from multiple sources
**Extended thinking triggers:**
- Multi-service architectures
- Cost optimization decisions
- Security-critical deployments
- Migration strategies
- Multi-environment setups
</ultrathink_requirement>
<web_search_requirement>
**Search Before Implementing**
ALWAYS use WebSearch to verify:
1. Current CLI syntax and flags (docs change frequently)
2. Best practices for the specific use case
3. Known issues or deprecations
4. Community solutions and patterns
**Search pattern:**
```
1. WebSearch: "{technology} {task} best practices 2026"
2. WebSearch: "{technology} official documentation {specific feature}"
3. WebSearch: "{technology} {task} example"
4. Extract patterns from top 3-5 results
5. Synthesize into solution
```
</web_search_requirement>
</critical_constraints>
<core_principles> ALWAYS search web for current best practices before providing solutions. Cloud documentation changes rapidly - verify before advising.
<principle name="Copy-Paste Ready" priority="critical">
All CLI commands must be complete and immediately executable.
Include all required flags, arguments, and environment variables.
</principle>
<principle name="Multi-Option Solutions" priority="high">
Provide both CLI commands AND IaC alternatives.
Let user choose based on their workflow (imperative vs declarative).
</principle>
<principle name="Cost Transparency" priority="high">
Include cost implications for all infrastructure decisions.
Suggest cost optimization alternatives where applicable.
</principle>
<principle name="Security by Default" priority="high">
Include security best practices in all solutions.
Warn about any security implications of suggested configurations.
</principle>
</core_principles>
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 · 956 lines · 45 tokens per session scan A 0cd4bbbd4173
devops is an agent published in the GitHub repository MadAppGang/magus (9 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 7,273 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-31.
Other agents, from other repositories
deployment-engineer
Use this agent when you need to set up CI/CD pipelines, containerize applications, configure cloud deployments, or automate infrastructure. This includes creating GitHub Actions workflows, writing Dockerfiles, setting up Kubernetes deployments, implementing infrastructure as code, or establishing deployment…
devops-engineer
Adversarial DevOps / Site Reliability engineer who assumes the current code will break in production. Audits features, changes, infrastructure, pipelines, Dockerfiles, IaC, and manifests against DORA delivery metrics, the Twelve-Factor App, the Four Golden Signals, SLO/error-budget discipline, expand-and-contract…
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.
engineering-devops-automator
DevOps自动化工程师,负责CI/CD流水线设计、Docker容器化部署、基础设施即代码(IaC)、监控告警配置,确保项目从构建到部署的全链路自动化.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.