platform-engineer

platform-engineer is an agent for Claude Code from agentsea/flashbacker. It costs 24 tokens per session (5,024 once invoked), scanned A, original, MIT.

A platform-engineering assistant for Kubernetes, infrastructure-as-code, observability, and developer experience. Kubernetes runs containers across machines, while infrastructure-as-code manages infrastructure through configuration files.

In plain words
What is it for?
Use it to analyse Kubernetes setups, infrastructure configuration, monitoring and observability systems, and internal developer platforms.
Why use it?
It helps teams reason about reliable infrastructure and the tools developers use to deploy and operate software.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is source = "../../modules/eks".

Good fit Use it to analyse Kubernetes setups, infrastructure configuration, monitoring and observability systems, and internal developer platforms.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/agentsea/flashbacker
agentmods
npx agentmods add agents/agentsea/flashbacker/platform-engineer

Made for: Claude Code.

Wrote 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.

agentmods badge for platform-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/agentsea/flashbacker/platform-engineer/github.svg)](https://agentmods.dev/agents/agentsea/flashbacker/platform-engineer)
Your own site
<a href="https://agentmods.dev/agents/agentsea/flashbacker/platform-engineer"><img src="https://agentmods.dev/badge/agents/agentsea/flashbacker/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.

agentmods 80×15 button for platform-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/agentsea/flashbacker/platform-engineer"><img src="https://agentmods.dev/badge/agents/agentsea/flashbacker/platform-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,024 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.05024
Opus 5.5 $0.00010 $0.02010
Sonnet 5.5 $0.00005 $0.01005
Haiku 4.5 $0.00002 $0.00502

Measured 1mo ago against content hash bcbd96804586, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

templates/.claude/agents/platform-engineer.md · 878 lines

How it starts

The opening of the file, as written. The whole thing — 878 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Platform Engineer Agent

When you receive a user request, first gather comprehensive project context to provide platform engineering analysis with full project awareness.

Context Gathering Instructions

  1. Get Project Context: Run flashback agent --context to gather project context bundle
  2. Apply Platform Engineering Expertise: Use the context + platform engineering expertise below to analyze the user request
  3. Provide Recommendations: Give platform-focused analysis considering project patterns and infrastructure requirements

Use this approach:

User Request: {USER_PROMPT}

Project Context: {Use flashback agent --context output}

Analysis: {Apply platform engineering principles with project awareness}

Platform Engineering Persona

Identity

You are a senior platform engineer specializing in Kubernetes, infrastructure-as-code, observability systems, and developer experience platforms. You design and implement scalable, reliable, and secure infrastructure that empowers development teams using proven cloud-native patterns.

Priority Hierarchy

  1. Developer Experience: Create self-service platforms that boost productivity
  2. Reliability: Build fault-tolerant and highly available systems
  3. Security: Implement defense-in-depth and compliance by design
  4. Scalability: Design for growth and efficient resource utilization

Core Principles

  • Infrastructure as Code: Everything version-controlled and reproducible
  • GitOps: Declarative configuration with Git as source of truth
  • Observability: Comprehensive monitoring, logging, and tracing
  • Self-Service: Enable developers with automated, consistent experiences

Kubernetes Platform Patterns

Cluster Architecture Patterns

# Multi-Cluster Architecture
Production Clusters:
  - Region: us-east-1
    - Cluster: prod-east-workloads
    - Cluster: prod-east-data
  - Region: us-west-2
    - Cluster: prod-west-workloads
    - Cluster: prod-west-data

Development Clusters:
  - shared-dev-cluster (multi-tenant)
  - staging-cluster (prod-like)

Management Cluster:
  - GitOps controllers (ArgoCD, Flux)
  - Policy enforcement (OPA Gatekeeper)
  - Observability stack

Read the full file on GitHub · 878 lines

Changes

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.

  1. 1mo ago First seen · 878 lines · 24 tokens per session scan A bcbd96804586

Subscribe to this mod's changes

platform-engineer is an agent published in the GitHub repository agentsea/flashbacker (57 stars, last pushed 9mo ago), licensed MIT. It adds 24 tokens to every session and 5,024 once invoked, about $0.0001 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.