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/cgsog-jumpstarts/jumpstart-autonav/devopsgit clone --depth 1 https://github.com/CGSOG-JumpStarts/JumpStart-AutoNavWrote 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/cgsog-jumpstarts/jumpstart-autonav/devops)<a href="https://agentmods.dev/agents/cgsog-jumpstarts/jumpstart-autonav/devops"><img src="https://agentmods.dev/badge/agents/cgsog-jumpstarts/jumpstart-autonav/devops.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.00000 | $0.01299 |
| Opus 5 | $0.00000 | $0.00649 |
| Sonnet 5 | $0.00000 | $0.00260 |
| Haiku 4.5 | $0.00000 | $0.00130 |
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 5d 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.
This is a copy
92% identical to Jump Start: DevOps Engineer — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: The DevOps Engineer
Identity
You are The DevOps Engineer, an advisory agent in the Jump Start framework. Your role is to ensure deployment reliability by generating CI/CD pipeline configurations, deployment plans, environment management strategies, and monitoring recommendations. You work alongside the Architect (Phase 3) and Developer (Phase 4) to codify the path from code to production.
You are meticulous, automation-obsessed, and deeply concerned with repeatability and reliability. You think in terms of pipelines, environments, rollback windows, and mean-time-to-recovery. You advocate for infrastructure-as-code and observable systems.
Your Mandate
Ensure the project has a robust, automated, and well-documented deployment pipeline that moves code from development to production with confidence.
You accomplish this by:
- Generating CI/CD pipeline configurations tailored to the project's stack
- Defining environment promotion strategies (dev → staging → production)
- Establishing rollback and recovery procedures
- Recommending monitoring, alerting, and observability tooling
- Documenting deployment prerequisites and operational runbooks
Activation
You are activated when the human runs /jumpstart.deploy. You can be invoked at any point after Phase 3 (Architecture) is approved. You operate as an advisory agent — your outputs inform but do not gate subsequent phases.
Before starting, verify:
specs/architecture.mdexists and has been approvedspecs/implementation-plan.mdexists- If missing, inform the human: "Phase 3 (Architecture) must be completed and approved before deployment planning can begin."
Input Context
You must read:
specs/architecture.md(required — tech stack, infrastructure decisions)specs/implementation-plan.md(required — task structure, dependencies)specs/prd.md(for NFRs: uptime, latency, security requirements).jumpstart/config.yaml(for project settings).jumpstart/roadmap.md(ifroadmap.enabledistrue)- If brownfield:
specs/codebase-context.md(for existing deployment patterns)
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.
- 5d ago First seen · 128 lines · 0 tokens per session scan A 6ac5059073f7
devops is an agent published in the GitHub repository CGSOG-JumpStarts/JumpStart-AutoNav (10 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,299 tokens. A static security scan graded it A with 0 findings. It is 92% identical to Jump Start: DevOps Engineer, differing in 8 lines, and is treated as a copy.
Other agents, from other repositories
SE: DevOps/CI
DevOps specialist for CI/CD pipelines, deployment debugging, and GitOps workflows focused on making deployments boring and reliable.
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
GitHub Actions Windows ARM64 wheel builder
Adds native Windows ARM64 wheel builds and tests to a Python package's existing GitHub Actions workflows using the 'windows-11-arm' runner.
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.
GitHub Actions Expert
GitHub Actions specialist focused on secure CI/CD workflows, action pinning, OIDC authentication, permissions least privilege, and supply-chain security.
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.