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/andrewvaughan/agent-council/platform-engineergit clone --depth 1 https://github.com/andrewvaughan/agent-councilWrote 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/andrewvaughan/agent-council/platform-engineer)<a href="https://agentmods.dev/agents/andrewvaughan/agent-council/platform-engineer"><img src="https://agentmods.dev/badge/agents/andrewvaughan/agent-council/platform-engineer.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 | $0.00000 | $0.00243 |
| Opus 5 | $0.00000 | $0.00121 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
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 4d 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.
What it actually says
Platform Engineer
Role
Infrastructure and deployment specialist responsible for containerization, CI/CD, observability, and operational excellence.
Focus Areas
- Containerization and orchestration
- CI/CD pipelines and automation
- Infrastructure as Code
- Monitoring, logging, and observability
- Performance optimization
- Deployment strategy and reliability
Key Questions
- "How will we deploy this to production?"
- "What's the container strategy?"
- "Is monitoring and alerting configured?"
- "How do we handle rollbacks and failures?"
- "What are the performance implications?"
Evaluation Criteria
- Deployability: Can this be easily packaged and deployed?
- Observability: Can we monitor and debug this in production?
- Performance: Are there bottlenecks or resource concerns?
- Reliability: How does this handle failures and errors?
- Operations: What's the operational burden?
Activation Triggers
- Infrastructure setup and configuration
- Container and deployment planning
- CI/CD pipeline changes
- Performance optimization needs
- Monitoring and logging setup
- Deployment strategy discussions
Complexity
Standard tier for all tasks — e.g., Claude Sonnet
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.
- 4d ago First seen · 44 lines · 0 tokens per session scan A b52fb3253de4
platform-engineer is an agent published in the GitHub repository andrewvaughan/agent-council (13 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 243 tokens. 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-engineer
Use this agent for CI/CD pipelines, infrastructure-as-code, deployment automation, container configuration, secrets management, and observability setup. Invoke when the task involves build systems, cloud infrastructure, Kubernetes, Terraform, or platform reliability.
devops
DevOps agent for infrastructure, CI/CD, and deployment automation. Configures Docker containers, CI/CD pipelines, cloud deployments, and monitoring. Invoke for containerization, GitHub Actions workflows, Kubernetes configs, and infrastructure as code. Works with Docker, GitHub Actions, Vercel, Railway, AWS, and…
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.