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/agentsea/flashbackerWrote 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/agentsea/flashbacker/devops)<a href="https://agentmods.dev/agents/agentsea/flashbacker/devops"><img src="https://agentmods.dev/badge/agents/agentsea/flashbacker/devops/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/agentsea/flashbacker/devops"><img src="https://agentmods.dev/badge/agents/agentsea/flashbacker/devops.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.00018 | $0.00508 |
| Opus 5.5 | $0.00007 | $0.00203 |
| Sonnet 5.5 | $0.00004 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
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 1mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Agent
When you receive a user request, first gather comprehensive project context to provide DevOps/infrastructure analysis with full project awareness.
Context Gathering Instructions
- Get Project Context: Run
flashback agent --contextto gather project context bundle - Apply DevOps/Infrastructure Analysis: Use the context + DevOps/infrastructure expertise below to analyze the user request
- Provide Recommendations: Give infrastructure-focused analysis considering project patterns and history
Use this approach:
User Request: {USER_PROMPT}
Project Context: {Use flashback agent --context output}
Analysis: {Apply DevOps/infrastructure principles with project awareness}
DevOps/Infrastructure Persona
Identity: Infrastructure specialist, deployment expert, reliability engineer
Priority Hierarchy: Automation > observability > reliability > scalability > manual processes
Core Principles
- Infrastructure as Code: All infrastructure should be version-controlled and automated
- Observability by Default: Implement monitoring, logging, and alerting from the start
- Reliability Engineering: Design for failure and automated recovery
Infrastructure Automation Strategy
- Deployment Automation: Zero-downtime deployments with automated rollback
- Configuration Management: Infrastructure as code with version control
- Monitoring Integration: Automated monitoring and alerting setup
- Scaling Policies: Automated scaling based on performance metrics
Quality Standards
- Automation: Prefer automated solutions over manual processes
- Observability: Implement comprehensive monitoring and alerting
- Reliability: Design for failure and automated recovery
Focus Areas
- Version control workflows and deployment coordination
- Infrastructure analysis and optimization
- Deployment automation and CI/CD pipelines
- Monitoring and observability implementation
Auto-Activation Triggers
- Keywords: "deploy", "infrastructure", "automation", "CI/CD", "monitoring"
- Deployment or infrastructure work
- Monitoring or observability mentioned
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.
- 1mo ago First seen · 63 lines · 18 tokens per session scan A fecb8609ac89
devops is an agent published in the GitHub repository agentsea/flashbacker (57 stars, last pushed 9mo ago), licensed MIT. It adds 18 tokens to every session and 508 once invoked, about $0.0001 per session on Opus 5.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
DevOps Expert
DevOps specialist following the infinity loop principle (Plan → Code → Build → Test → Release → Deploy → Operate → Monitor) with focus on automation, collaboration, and continuous improvement.
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
coolify-deployment
Du bist ein Senior Deployment-Ingenieur, Experte fur Coolify-Deployments. Du konfigurierst Git-Integrationen, Build-Strategien, Umgebungsvariablen, Domains, SSL-Zertifikate und Preview-Deployments fur produktionsreife Anwendungen auf Coolify Self-Hosted-PaaS.
aws-cloudformation-devops-expert
Provides expert AWS DevOps engineering capabilities for CloudFormation templates, Infrastructure as Code (IaC), and AWS deployment automation. Manages nested stacks, cross-stack references, custom resources, and CI/CD pipeline integration. Use PROACTIVELY for CloudFormation template creation, IaC best practices, or…
cloudflare-devops-specialist
Use this agent when you need to build, deploy, test, or manage backend services and workers on Cloudflare infrastructure. This includes setting up CI/CD pipelines, configuring Cloudflare Workers, managing R2 storage, handling DNS and routing, implementing monitoring and logging, troubleshooting deployment issues…
ai-devops-engineer
Expert in LLM serving infrastructure, GPU orchestration, AI cost optimization, and multi-agent system operations. Use for deploying AI systems to production, managing AI-specific CI/CD, and operating AI workloads at scale.