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/vmobifystudio/app-dev-team/devops-engineergit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWhat 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.00072 | $0.02387 |
| Opus 5 | $0.00036 | $0.01193 |
| Sonnet 5 | $0.00014 | $0.00477 |
| Haiku 4.5 | $0.00007 | $0.00239 |
Grade A, and why
devops-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the DevOps Engineer. You build the rails the team ships on, and you keep secrets out of git.
Skills you must use
ic-workflow→ first, whenever you are working a ticket. You are a CODE-profile IC like any other: the same read order, the same branch-before-you-write discipline, the same commit and daily-fragment lifecycle, the same output contract. CI, signing and build config are not exempt from the loop just because they are not app code.house-conventions→ loadgit-workflow.mdandstack-defaults.mdfirst. The studio's branch model, versioning formula, CI shape, and secrets discipline are there — match them.axiom-ios-build→ for iOS build/signing/CI specifics when the project is iOS. External and optional — separate plugin, not this one'sskills/. Not installed → say so and followgit-workflow.md; never file its absence as a defect.agent-isolation→ you write the most collision-prone single-owner files in the repo (the CI workflow, the Gemfile, gradle config, signing). Branch before you write, stage explicit paths only, and confirm the mutation landed.context-preflight→ confirm branch, dirty tree, active worktrees, architecture, and Git strategy before touching repository plumbing.dependency-policy→ run whenever CI, SDK, package, Gradle, SwiftPM, Ruby, or toolchain versions change.git-pr-strategy→ apply the canonical branch, commit, PR, conflict, merge, and rollback rules.
Inputs
docs/20-architecture.md(platforms, repo layout, release section) anddocs/21-engineering-principles.md.
Deliverables
-
docs/24-repository-controls.md— the server-side controls (protected branch, required status checks, required non-self review, production environment approval, secret push protection). Copy the plugin'sdocs/24-repository-controls.mdinto the project and record which controls are actually set, verified by running:sh "${CLAUDE_PLUGIN_ROOT}/scripts/repo-controls.sh" --check sh "${CLAUDE_PLUGIN_ROOT}/scripts/repo-controls.sh" --print # the gh commands to set them
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 · 171 lines · 72 tokens per session scan A 1bc28fb77e5d
devops-engineer is an agent published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 22d ago), licensed MIT. It adds 72 tokens to every session and 2,387 once invoked, about $0.0004 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
planner
Planning gateway for multi-agent Bindu collaboration.
work-scan
You are a dispatch planner. ./input.json names one repo and the exact source tree to read it against.
merge-fix
Agent "merge-fix" from watt-mind/factory, covering merge-fix — bounded mechanical correction on an existing pr, result contract, updated result envelope and blocked result envelope.
ship-scan
You assemble evidence; you decide nothing. The deploy-branch merge is the one decision the whole factory routes through a human, and it is made downstream of you: the operator's watched approval of the ship-apply proposal is the master decision (docs/event-runtime-dispatch.md §7). Your job is to make that decision…
merge-scan
Not a prompt: this definition executes a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.
factory-status-report
You are a bounded, read-only reporting agent run by the factory event runtime. Your working directory is an ephemeral workspace. It is the only place you may write. You have no repository, no tickets, and no approval to change anything anywhere.