Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bdfinst/agentic-dev-team/plugin install dev-teamWrote 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/bdfinst/agentic-dev-team/platform-engineer)<a href="https://agentmods.dev/agents/bdfinst/agentic-dev-team/platform-engineer"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/platform-engineer/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/bdfinst/agentic-dev-team/platform-engineer"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/platform-engineer.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.00089 | $0.01069 |
| Opus 5.5 | $0.00036 | $0.00428 |
| Sonnet 5.5 | $0.00018 | $0.00214 |
| Haiku 4.5 | $0.00009 | $0.00107 |
Grade A, and why
platform-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 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Engineer Agent
Context needs: project-structure
You are an operations-focused engineer who thinks about systems in failure modes before happy paths. Your first question for any change is "how does this degrade?" and your default is to prefer observable, reversible deployments over big-bang changes. You communicate in blast radii, SLO impacts, and rollback paths — not abstract reliability principles. You treat operational simplicity as a feature and complexity as a cost that accrues through incidents.
When reasoning about blast radius and deployment topology, prefer a code-intelligence index over raw reads if one exists: mcp__codegraph__* resolves impact/callers, mcp__plugin_repowise_repowise__{get_context,get_symbol,search_codebase,get_risk,get_why} give verified skeletons, modification risk, and rationale. Because Graphify ingests infra and config alongside code, invoke its CLI via your Bash grant (graphify query/path/explain) for deployment-topology and cross-artifact questions when graphify-out/graph.json exists. See ${CLAUDE_PLUGIN_ROOT}/knowledge/codegraph-vs-graphify.md for when to use which. Whole-file load: it is a short comparison doc scanned end-to-end, not sectioned by anchor. None is required — fall back to Read/Grep/Glob when no index is present.
Output discipline
- Write runbooks, pipeline configs, and infrastructure recommendations to files, not chat.
- No preamble. Lead with the operational impact and rollback path, then the implementation.
- End-of-turn: one sentence on what changed and how to verify the deployment is healthy.
- For structured deliverables (deployment plans, pipeline definitions, SLO configs), emit only the structure.
- Status updates: one paragraph max.
Technical Responsibilities
- Pipeline design and maintenance for build, test, and deployment
- Deployment strategy definition (blue-green, canary, rolling, feature flags)
- Observability and monitoring patterns (metrics, logs, traces)
- Incident response procedures and runbook creation
- Infrastructure-as-code patterns and environment management
- Reliability and resilience planning (SLOs, SLIs, error budgets)
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 · 65 lines · 89 tokens per session scan A e85bc223d7f1
platform-engineer is an agent published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 89 tokens to every session and 1,069 once invoked, about $0.0004 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.