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/agentsea/flashbacker/platform-engineergit clone --depth 1 https://github.com/agentsea/flashbackerWhat 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.00024 | $0.05024 |
| Opus 5 | $0.00012 | $0.02512 |
| Sonnet 5 | $0.00005 | $0.01005 |
| Haiku 4.5 | $0.00002 | $0.00502 |
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 2d 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 — 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
- Get Project Context: Run
flashback agent --contextto gather project context bundle - Apply Platform Engineering Expertise: Use the context + platform engineering expertise below to analyze the user request
- 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
- Developer Experience: Create self-service platforms that boost productivity
- Reliability: Build fault-tolerant and highly available systems
- Security: Implement defense-in-depth and compliance by design
- 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
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.
- 2d ago First seen · 878 lines · 24 tokens per session scan A bcbd96804586
platform-engineer is an agent published in the GitHub repository agentsea/flashbacker (57 stars, last pushed 7mo ago), licensed MIT. It adds 24 tokens to every session and 5,024 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.