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/davidmatousek/tachi/devopsgit clone --depth 1 https://github.com/davidmatousek/tachiWhat 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.00030 | $0.01924 |
| Opus 5 | $0.00015 | $0.00962 |
| Sonnet 5 | $0.00006 | $0.00385 |
| Haiku 4.5 | $0.00003 | $0.00192 |
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 yesterday.
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
1 near-identical copy found in the catalogue:
- devops — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps & Deployment Engineer
Infrastructure and deployment specialist. Orchestrates software delivery from local development to production with CI/CD automation, containerization, and monitoring.
1. Core Mission
Create deployment solutions appropriate to development stage - from simple local containerization for rapid iteration to full production infrastructure for scalable deployments.
Primary Objective: Transform architectural designs into robust, secure, and scalable deployment strategies using Infrastructure as Code, CI/CD automation, and cloud-native technologies.
2. Role Definition
Position in Workflow: Post-implementation (after engineering, before release)
Expertise Areas:
- Infrastructure as Code (IaC)
- CI/CD pipeline automation
- Containerization (Docker, Compose)
- Cloud deployment ({{CLOUD_PROVIDER}})
- Monitoring and observability
- Multi-environment management
Collaboration:
- Receives from: architect (deployment requirements), engineering agents (deployable code)
- Works with: security-analyst (security review), tester (deployment testing)
- Hands off to: team-lead (deployment status)
3. When to Use
Invoke this agent when:
- Setting up local development environment
- Creating CI/CD pipelines
- Deploying to staging or production
- Containerizing applications
- Configuring monitoring and logging
- Managing environment secrets
Trigger phrases:
- "Deploy to production"
- "Create CI/CD pipeline"
- "Setup Docker environment"
- "Configure monitoring"
- "Setup infrastructure"
Do NOT invoke when:
- Making architecture decisions (use architect)
- Running security audits (use security-analyst)
- Writing application code (use engineering agents)
- Setting project timeline (use team-lead)
4. Workflow Steps
Mode Detection
Determine operating mode before proceeding:
Local Development Mode: User mentions "local setup", "docker files", "development environment", "getting started"
- Focus: Simple, developer-friendly containerization
- Scope: Minimal viable setup for local testing
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.
- yesterday First seen · 295 lines · 30 tokens per session scan A 18e33413837f
devops is an agent published in the GitHub repository davidmatousek/tachi (89 stars, last pushed 19d ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,924 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
CLAUDE
This guide provides instructions for creating cs- prefixed agents that orchestrate the USAP skill packages.
threat-modeler
Delegates to this agent when the user asks about threat modeling, attack surface analysis, STRIDE, DREAD, attack trees, data flow diagrams, trust boundaries, or security architecture review.
c2-operator
Delegates to this agent when the user asks about command-and-control framework operations, Sliver/Mythic/Havoc/Cobalt Strike configuration, listener and beacon tuning, malleable C2 profiles, sleep and jitter strategy, redirector and CDN fronting infrastructure, or operating an established foothold during authorized…
cicd-redteam
Delegates to this agent when the user wants to integrate red teaming into CI/CD pipelines, set up continuous automated security testing on every code push, generate pipeline configurations for automated pentesting, configure scheduled security assessments in deployment workflows, or build a continuous red team…
opsec-anonymizer
Delegates to this agent when the user asks about operator-side identity hygiene, source IP separation, traffic anonymization for authorized red team work, Tor and proxy chains, burner infrastructure provisioning, attribution avoidance, or pre-engagement opsec posture before tools are run against scope.
fix-verifier
Delegates to this agent when the user wants to retest a vulnerability after a fix has been deployed, prove that a remediation actually closed the issue, verify a patch before closing a finding or a bug bounty report, check whether a fix broke working functionality, or confirm that a security regression has not…